search for: 196428c

fix a code style in drivers/char/virtio_console.c Signed-off-by: Liu Qi <lingjiujianke at gmail.com> --- drivers/char/virtio_console.c | 7 +------ 1 files changed, 1 insertions(+), 6 deletions(-) diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c index 196428c..61dad7e 100644 --- a/drivers/char/virtio_console.c +++ b/drivers/char/virtio_console.c @@ -1299,36 +1299,31 @@ static int init_vqs(struct ports_device *portdev) char **io_names; struct virtqueue **vqs; u32 i, j, nr_ports, nr_queues; - int err; + int err = -ENOME...

fix a code style in drivers/char/virtio_console.c Signed-off-by: Liu Qi <lingjiujianke at gmail.com> --- drivers/char/virtio_console.c | 7 +------ 1 files changed, 1 insertions(+), 6 deletions(-) diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c index 196428c..61dad7e 100644 --- a/drivers/char/virtio_console.c +++ b/drivers/char/virtio_console.c @@ -1299,36 +1299,31 @@ static int init_vqs(struct ports_device *portdev) char **io_names; struct virtqueue **vqs; u32 i, j, nr_ports, nr_queues; - int err; + int err = -ENOME...

Hello, This series reworks the ABI to allow port discovery (only) via the control queue and enable multiport again. In addition, it adds support for non-blocking write() support, which means no spinning. This works fine with the recent patches that are on qemu-devel. Also included is removal of hvc_remove() as removing one such console port causes other console ports (registered with hvc) to

Hello, This series reworks the ABI to allow port discovery (only) via the control queue and enable multiport again. In addition, it adds support for non-blocking write() support, which means no spinning. This works fine with the recent patches that are on qemu-devel. Also included is removal of hvc_remove() as removing one such console port causes other console ports (registered with hvc) to

virtqueue ops were introduced in the hope that we'll have multiple implementations besides virtio_ring, but none have surfaced so far, and given that existing virtio ring is deployed in production we are likely stuck with it now, so this layer just adds complexity and overhead. Further, the need to pass vq twice to each call (as in dev->vq->vq_ops->kick(dev->vq) ) adds potential

virtqueue ops were introduced in the hope that we'll have multiple implementations besides virtio_ring, but none have surfaced so far, and given that existing virtio ring is deployed in production we are likely stuck with it now, so this layer just adds complexity and overhead. Further, the need to pass vq twice to each call (as in dev->vq->vq_ops->kick(dev->vq) ) adds potential