From: Isaku Yamahata <yamahata@valinux.co.jp>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] pci: fix pci_find_space()
Date: Mon, 12 Apr 2010 10:59:40 +0900 [thread overview]
Message-ID: <20100412015940.GC1232@valinux.co.jp> (raw)
In-Reply-To: <20100411091930.GC7383@redhat.com>
On Sun, Apr 11, 2010 at 12:19:30PM +0300, Michael S. Tsirkin wrote:
> On Fri, Apr 09, 2010 at 07:20:48PM +0900, Isaku Yamahata wrote:
> > pci capability must be in PCI space.
> > It can't lay in PCIe extended config space.
> >
> > Cc: "Michael S. Tsirkin" <mst@redhat.com>
> > Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
>
> I guess the point is that we'll need another API to allocate
> extended capabilities?
That's right. I have those in my local repo.
--
yamahata
prev parent reply other threads:[~2010-04-12 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 10:20 [Qemu-devel] [PATCH] pci: fix pci_find_space() Isaku Yamahata
2010-04-11 9:19 ` [Qemu-devel] " Michael S. Tsirkin
2010-04-12 1:59 ` 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=20100412015940.GC1232@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=mst@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).