From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: Alon Levy <alevy@redhat.com>, qemu list <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PULL] virtio-serial: fixes, cleanups
Date: Tue, 18 Dec 2012 17:49:27 -0600 [thread overview]
Message-ID: <878v8uyl88.fsf@codemonkey.ws> (raw)
In-Reply-To: <20121218101943.GK21639@amit.redhat.com>
Amit Shah <amit.shah@redhat.com> writes:
> Hi Anthony,
>
> Please pull to get fixes and cleanups to virtio-serial code.
>
Pulled. Thanks.
Regards,
Anthony Liguori
> Thanks,
>
> The following changes since commit 1c97e303d4ea80a2691334b0febe87a50660f99d:
>
> Merge remote-tracking branch 'afaerber/qom-cpu' into staging (2012-12-10 08:35:15 -0600)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/virt/qemu/amit/virtio-serial.git master
>
> for you to fetch changes up to 91bdd1cf08f65b7a127c22d4d65ff9d16dcac870:
>
> virtio-serial-bus: assert port is non-null in remove_port() (2012-12-18 14:28:50 +0530)
>
> ----------------------------------------------------------------
> Amit Shah (6):
> virtio-serial: use uint32_t to count ports
> virtio-serial: move active ports loading to separate function
> virtio-serial: allocate post_load only at load-time
> virtio-serial: delete timer if active during exit
> virtio-serial-bus: send_control_msg() should not deal with cpkts
> virtio-serial-bus: assert port is non-null in remove_port()
>
> hw/virtio-serial-bus.c | 195 ++++++++++++++++++++++++++++++++++++++++++-------------------------------
> 1 file changed, 113 insertions(+), 82 deletions(-)
>
> Amit
prev parent reply other threads:[~2012-12-18 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 10:19 [Qemu-devel] [PULL] virtio-serial: fixes, cleanups Amit Shah
2012-12-18 23:49 ` Anthony Liguori [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=878v8uyl88.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alevy@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@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).