virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: virtualization@lists.linux-foundation.org
Cc: Amit Shah <amit.shah@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [PATCH 0/8] (v4) virtio: console: Fixes, new way of discovering ports
Date: Tue, 23 Mar 2010 18:23:08 +0530	[thread overview]
Message-ID: <1269348796-8660-1-git-send-email-amit.shah@redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

Hello,

This version addresses comments by Gerd and Michael:
- instead of returning -EPIPE if host is not connected in the write
  case, just block the write if it's a blocking file and return -EAGAIN
  if it's non-blocking.

- Removes early_console_printk after the first console is found

- Adds early_put_chars fix by François Diakhaté. It still needs a
  sign-off by him.

Standard message: Since the ABI is being reworked, it's essential to
push this to 2.6.34 so that we're not left supporting the older
interface.

Amit Shah (7):
  MAINTAINERS: Put the virtio-console entry in correct alphabetical
    order
  virtio: console: Remove config work handler
  virtio: console: Add a __send_control_msg() that can send messages
    without a valid port
  virtio: console: Move code around for future patches
  virtio: console: Use a control message to add ports
  virtio: console: Don't always create a port 0 if using multiport
  virtio: console: Add partial blocking/non-blocking support to write()

François Diakhaté (1):
  virtio: console: Fix early_put_chars usage

 MAINTAINERS                    |   13 +-
 drivers/char/virtio_console.c  |  447 ++++++++++++++++++----------------------
 include/linux/virtio_console.h |   18 +-
 3 files changed, 215 insertions(+), 263 deletions(-)


[-- Attachment #2: Type: text/plain, Size: 184 bytes --]

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/virtualization

             reply	other threads:[~2010-03-23 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 12:53 Amit Shah [this message]
2010-03-23 12:53 ` [PATCH 1/8] MAINTAINERS: Put the virtio-console entry in correct alphabetical order Amit Shah
2010-03-23 12:53   ` [PATCH 2/8] virtio: console: Remove config work handler Amit Shah
2010-03-23 12:53     ` [PATCH 3/8] virtio: console: Add a __send_control_msg() that can send messages without a valid port Amit Shah
2010-03-23 12:53       ` [PATCH 4/8] virtio: console: Move code around for future patches Amit Shah
2010-03-23 12:53         ` [PATCH 5/8] virtio: console: Use a control message to add ports Amit Shah
2010-03-23 12:53           ` [PATCH 6/8] virtio: console: Don't always create a port 0 if using multiport Amit Shah
2010-03-23 12:53             ` [PATCH 7/8] virtio: console: Fix early_put_chars usage Amit Shah
2010-03-23 12:53               ` [PATCH 8/8] virtio: console: Add partial blocking/non-blocking support to write() Amit Shah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1269348796-8660-1-git-send-email-amit.shah@redhat.com \
    --to=amit.shah@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).