All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: qemu list <qemu-devel@nongnu.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] virtio-console: no need to remove char handlers explicitly
Date: Fri, 13 Jan 2012 15:28:05 +0530	[thread overview]
Message-ID: <20120113095805.GB9506@amit.redhat.com> (raw)
In-Reply-To: <915d33eb055b4d388fda85c385b459e5631f91fe.1326448314.git.amit.shah@redhat.com>

On (Fri) 13 Jan 2012 [15:24:59], Amit Shah wrote:
> qdev is now equipped (thanks to the last commit) to disassociate
> chardevs from the qdev devices on the devices going away.  So doing it
> in the virtio-console driver is not necessary.
> 
> Since that was the only thing being done in the qdev exit method, drop
> it entirely.

Commit message is correct, patch is not.  Updated patch coming soon..

> diff --git a/hw/virtio-console.c b/hw/virtio-console.c
> index 73d866a..9275fd9 100644
> --- a/hw/virtio-console.c
> +++ b/hw/virtio-console.c
> @@ -127,16 +127,6 @@ static int virtconsole_initfn(VirtIOSerialPort *port)
>  
>  static int virtconsole_exitfn(VirtIOSerialPort *port)
>  {
> -    VirtConsole *vcon = DO_UPCAST(VirtConsole, port, port);
> -
> -    if (vcon->chr) {
> -	/*
> -	 * Instead of closing the chardev, free it so it can be used
> -	 * for other purposes.
> -	 */
> -	qemu_chr_add_handlers(vcon->chr, NULL, NULL, NULL, NULL);
> -    }
> -
>      return 0;
>  }

		Amit

      reply	other threads:[~2012-01-13  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13  9:54 [Qemu-devel] [PATCH 0/2] qdev: disassociate chardev from device on device exit Amit Shah
2012-01-13  9:54 ` [Qemu-devel] [PATCH 1/2] qdev: Add a 'free' method to disassociate chardev from qdev device Amit Shah
2012-01-13  9:54 ` [Qemu-devel] [PATCH 2/2] virtio-console: no need to remove char handlers explicitly Amit Shah
2012-01-13  9:58   ` Amit Shah [this message]

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=20120113095805.GB9506@amit.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.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.