qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/7] serial device hotplug patch series.
Date: Fri, 12 Oct 2012 11:42:01 +0200	[thread overview]
Message-ID: <5077E5E9.5090000@redhat.com> (raw)
In-Reply-To: <1350033962-16665-1-git-send-email-kraxel@redhat.com>

Il 12/10/2012 11:25, Gerd Hoffmann ha scritto:
> Final patch adds chardev hotplug to the mix, which makes the other
> patches alot more useful.  It is the missing bit needed to really
> hotplug serial devices:
> 
>    (qemu) chardev_add pciserial file /root/hotchardev.log
>    (qemu) device_add pci-serial,chardev=pciserial,id=pciserial
> 
> And the reverse:
> 
>    (qemu) device_del pciserial
>    (qemu) chardev_del pciserial
> 
> please review & pull,

I think the last patch is not ready, please wait for Luiz's review too.

>   Gerd
> 
> The following changes since commit b4ae3cfa57b8c1bdbbd7b7d420971e9171203ade:
> 
>   ssi: Add slave autoconnect helper (2012-10-10 11:13:32 +1000)
> 
> are available in the git repository at:
>   git://git.kraxel.org/qemu serial.1
> 
> Gerd Hoffmann (7):
>       serial: split serial.c
>       serial: add pci variant
>       serial: add windows inf file for the pci card to docs
>       serial: add 2x + 4x pci variant
>       usb-serial: don't magically zap chardev on umplug
>       usb-serial: only expose device in guest when the chardev is open
>       chardev: add hotplug support.

      parent reply	other threads:[~2012-10-12  9:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12  9:25 [Qemu-devel] [PULL 0/7] serial device hotplug patch series Gerd Hoffmann
2012-10-12  9:25 ` [Qemu-devel] [PATCH 1/7] serial: split serial.c Gerd Hoffmann
2012-10-12  9:25 ` [Qemu-devel] [PATCH 2/7] serial: add pci variant Gerd Hoffmann
2012-10-12  9:25 ` [Qemu-devel] [PATCH 3/7] serial: add windows inf file for the pci card to docs Gerd Hoffmann
2012-10-12  9:25 ` [Qemu-devel] [PATCH 4/7] serial: add 2x + 4x pci variant Gerd Hoffmann
2012-10-12  9:26 ` [Qemu-devel] [PATCH 5/7] usb-serial: don't magically zap chardev on umplug Gerd Hoffmann
2012-10-12  9:26 ` [Qemu-devel] [PATCH 6/7] usb-serial: only expose device in guest when the chardev is open Gerd Hoffmann
2012-10-12  9:26 ` [Qemu-devel] [PATCH 7/7] chardev: add hotplug support Gerd Hoffmann
2012-10-12  9:40   ` Paolo Bonzini
2012-10-12 10:23     ` Gerd Hoffmann
2012-10-12 10:50       ` Paolo Bonzini
2012-10-12 11:15         ` Gerd Hoffmann
2012-10-12 11:17           ` Paolo Bonzini
2012-10-12 12:37             ` Gerd Hoffmann
2012-10-12 12:39               ` [Qemu-devel] [PATCH v2] " Gerd Hoffmann
2012-10-12 13:12                 ` Gerd Hoffmann
2012-10-12 16:54                 ` Paolo Bonzini
2012-10-12 17:08                   ` Paolo Bonzini
2012-10-15  6:51                 ` Lei Li
2012-10-15 11:09                   ` Andreas Färber
2012-10-16 13:23                     ` Luiz Capitulino
2012-10-15 17:36                   ` Eric Blake
2012-10-16 14:02                     ` Paolo Bonzini
2012-10-12  9:42 ` Paolo Bonzini [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=5077E5E9.5090000@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@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 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).