From: "Michael S. Tsirkin" <mst@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: amit.shah@redhat.com, jan.kiszka@siemens.com,
qemu-devel@nongnu.org, yamahata@valinux.co.jp
Subject: Re: [Qemu-devel] [PULL] pci, virtio, net
Date: Wed, 3 Aug 2011 11:19:42 +0300 [thread overview]
Message-ID: <20110803081942.GA5606@redhat.com> (raw)
In-Reply-To: <m3wreuj4hk.fsf@blackfin.pond.sub.org>
On Wed, Aug 03, 2011 at 10:15:03AM +0200, Markus Armbruster wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > The following changes since commit d1afc48b7cfdb4490f322d5d82a2aae6d545ec06:
> >
> > SPARC64: implement addtional MMU faults related to nonfaulting load (2011-07-21 20:02:22 +0000)
> >
> > are available in the git repository at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git for_anthony
> >
> > Amit Shah (3):
> > virtio-blk: Fix memleak on exit
> > virtio-net: don't use vdev after virtio_cleanup
> > virtio: Plug memleak by freeing vdev
> >
> > Isaku Yamahata (1):
> > pcie_host: verify mmcfg address range
> >
> > Jan Kiszka (1):
> > pci: Common overflow prevention
> >
> > Markus Armbruster (2):
> > Fix automatically assigned network names for netdev
> > Fix netdev name lookup in -device, device_add, netdev_del
> >
> > Michael S. Tsirkin (1):
> > virtio-pci: use generic logic for command access
>
> Some of these (including mine) are obvious candidates for STABLE.
> Perhaps even all of them. Michael?
Amit's and your patches probably are. The pci changes probably aren't.
--
MST
next prev parent reply other threads:[~2011-08-03 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 14:27 [Qemu-devel] [PULL] pci, virtio, net Michael S. Tsirkin
2011-08-03 8:15 ` Markus Armbruster
2011-08-03 8:19 ` Michael S. Tsirkin [this message]
2011-08-04 21:45 ` Anthony Liguori
2011-08-04 22:44 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2012-03-15 23:49 Michael S. Tsirkin
2012-03-16 18:21 ` Anthony Liguori
2012-03-19 18:11 ` Anthony Liguori
2012-04-03 14:41 ` Michael S. Tsirkin
2012-04-05 12:03 ` Michael S. Tsirkin
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=20110803081942.GA5606@redhat.com \
--to=mst@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).