From: "Michael S. Tsirkin" <mst@redhat.com>
To: "M. Warner Losh" <imp@bsdimp.com>
Cc: aliguori@us.ibm.com, mtosatti@redhat.com, avi@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: questions on default_config_write in hw/pci.c
Date: Thu, 30 Apr 2009 20:33:02 +0300 [thread overview]
Message-ID: <20090430173302.GB16925@redhat.com> (raw)
In-Reply-To: <20090430.112820.48552365.imp@bsdimp.com>
On Thu, Apr 30, 2009 at 11:28:20AM -0600, M. Warner Losh wrote:
> The above is a bug. 0x80 is a bit that says "I have multiple
> functions" and is orthogonal to the type of device.
Ah. Thanks.
--
MST
next prev parent reply other threads:[~2009-04-30 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 16:15 [Qemu-devel] questions on default_config_write in hw/pci.c Michael S. Tsirkin
2009-04-30 16:35 ` [Qemu-devel] " Anthony Liguori
2009-04-30 17:15 ` Marcelo Tosatti
2009-04-30 17:28 ` M. Warner Losh
2009-04-30 17:33 ` Michael S. Tsirkin [this message]
2009-04-30 17:29 ` Michael S. Tsirkin
2009-04-30 17:45 ` Anthony Liguori
2009-04-30 19:26 ` Marcelo Tosatti
2009-05-01 4:50 ` M. Warner Losh
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=20090430173302.GB16925@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=imp@bsdimp.com \
--cc=mtosatti@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).