From: Isaku Yamahata <yamahata@valinux.co.jp>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: skandasa@cisco.com, etmartin@cisco.com, qemu-devel@nongnu.org,
wexu2@cisco.com
Subject: [Qemu-devel] Re: [PATCH 0/6] pcie: fixes for pci branch
Date: Thu, 28 Oct 2010 11:45:36 +0900 [thread overview]
Message-ID: <20101028024536.GF2243@valinux.co.jp> (raw)
In-Reply-To: <20101027164048.GA18035@redhat.com>
On Wed, Oct 27, 2010 at 06:40:48PM +0200, Michael S. Tsirkin wrote:
> On Wed, Oct 27, 2010 at 07:21:15PM +0900, Isaku Yamahata wrote:
> > This patch series fixes isseus which introduced by
> > 5704608988972359473ce609f9e4884808115b58
> > cd870502e228f8f028f93fb585ae3b208fcb46c7
> > 4b78560503a802eae3663ace9f9cf080319e7265
>
> OK, I applied this, except I basically backed out range check changes.
> Pls take a look at the branch, and test if possible -
> if OK with you I think we can merge this part.
I took a look at it. It looks good.
--
yamahata
prev parent reply other threads:[~2010-10-28 2:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 10:21 [Qemu-devel] [PATCH 0/6] pcie: fixes for pci branch Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 1/6] pcie: fix pcie_cap_slot_write_config() Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 2/6] pcie/slot: fix hotplug_event_notify() Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 3/6] pcie/slot: clean up of hotplug_event_notify() Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 4/6] pcie/slot: factor out the logic to update hotplug event status Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 5/6] pcie/slot: fix save/load Isaku Yamahata
2010-10-27 10:21 ` [Qemu-devel] [PATCH 6/6] msix: remove range checks Isaku Yamahata
2010-10-27 14:52 ` [Qemu-devel] " Michael S. Tsirkin
2010-10-27 16:40 ` [Qemu-devel] Re: [PATCH 0/6] pcie: fixes for pci branch Michael S. Tsirkin
2010-10-28 2:45 ` Isaku Yamahata [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=20101028024536.GF2243@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=etmartin@cisco.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=skandasa@cisco.com \
--cc=wexu2@cisco.com \
/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).