From: Anthony Liguori <anthony@codemonkey.ws>
To: David Ahern <daahern@cisco.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add close callback for tty-based char device
Date: Wed, 10 Feb 2010 16:51:20 -0600 [thread overview]
Message-ID: <4B733868.2040100@codemonkey.ws> (raw)
In-Reply-To: <1265839249-12068-1-git-send-email-daahern@cisco.com>
On 02/10/2010 04:00 PM, David Ahern wrote:
> Add a tty close callback. Right now if a guest device that is connected
> to a tty-based chardev in the host is removed, the tty is not closed.
> With this patch it is closed.
>
> Example use case is connecting an emulated USB serial cable in the guest
> to ttyS0 of the host using the monitor command:
>
> usb_add serial::/dev/ttyS0
>
> and then removing the device with:
>
> usb_del serial::/dev/ttyS0
>
> Signed-off-by: David Ahern<daahern@cisco.com>
> ---
> qemu-char.c | 15 +++++++++++++++
> 1 files changed, 15 insertions(+), 0 deletions(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index 75dbf66..77edec9 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -1173,6 +1173,20 @@ static int tty_serial_ioctl(CharDriverState *chr, int cmd, void *arg)
> return 0;
> }
>
> +static void qemu_chr_close_tty(CharDriverState *chr)
> +{
> + FDCharDriver *s = chr->opaque;
> + int fd = -1;
> +
> + if (s)
> + fd = s->fd_in;
>
>
You've got trailing spaces and this doesn't adhere to CODING_STYLE
(needs curly braces around the if clause).
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-02-10 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 22:00 [Qemu-devel] [PATCH] add close callback for tty-based char device David Ahern
2010-02-10 22:51 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-03 16:18 David S. Ahern
2010-02-10 18:45 ` Anthony Liguori
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=4B733868.2040100@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=daahern@cisco.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.