From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: QEMU-devel <qemu-devel@nongnu.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] PCI: Add PCI_EXP_TYPE_PCIE_BRIDGE value
Date: Thu, 23 Feb 2012 12:09:52 -0800 [thread overview]
Message-ID: <20120223120952.6d9915a1@jbarnes-desktop> (raw)
In-Reply-To: <1329841330-14902-1-git-send-email-anthony.perard@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On Tue, 21 Feb 2012 16:22:10 +0000
Anthony PERARD <anthony.perard@citrix.com> wrote:
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
>
> ---
> include/linux/pci_regs.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/pci_regs.h b/include/linux/pci_regs.h
> index e41a10f..4b608f5 100644
> --- a/include/linux/pci_regs.h
> +++ b/include/linux/pci_regs.h
> @@ -391,6 +391,7 @@
> #define PCI_EXP_TYPE_UPSTREAM 0x5 /* Upstream Port */
> #define PCI_EXP_TYPE_DOWNSTREAM 0x6 /* Downstream Port */
> #define PCI_EXP_TYPE_PCI_BRIDGE 0x7 /* PCI/PCI-X Bridge */
> +#define PCI_EXP_TYPE_PCIE_BRIDGE 0x8 /* PCI/PCI-X to PCIE Bridge */
> #define PCI_EXP_TYPE_RC_END 0x9 /* Root Complex Integrated Endpoint */
> #define PCI_EXP_TYPE_RC_EC 0xa /* Root Complex Event Collector */
> #define PCI_EXP_FLAGS_SLOT 0x0100 /* Slot implemented */
Applied, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-02-23 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 16:22 [Qemu-devel] PCI: Add PCI_EXP_TYPE_PCIE_BRIDGE value Anthony PERARD
2012-02-23 20:09 ` Jesse Barnes [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=20120223120952.6d9915a1@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=anthony.perard@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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).