From: Myron Stowe <myron.stowe@redhat.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, yuxiangl@marvell.com,
yxlraid@gmail.com, greg@kroah.com, alex.williamson@redhat.com,
kay@vrfy.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] PCI: Define macro for Marvell vendor ID
Date: Wed, 20 Mar 2013 22:34:56 -0600 [thread overview]
Message-ID: <20130321043456.7229.40987.stgit@amt.stowe> (raw)
In-Reply-To: <20130321043449.7229.81056.stgit@amt.stowe>
From: Xiangliang Yu <yuxiangl@marvell.com>
Define PCI_VENDOR_ID_MARVELL_EXT macro for 0x1b4b vendor ID
Signed-off-by: Xiangliang Yu <yuxiangl@marvell.com>
Signed-off-by: Myron Stowe <myron.stowe@redhat.com>
---
include/linux/pci_ids.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index f11c1c2..a80f9e6 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -1604,6 +1604,7 @@
#define PCI_SUBDEVICE_ID_KEYSPAN_SX2 0x5334
#define PCI_VENDOR_ID_MARVELL 0x11ab
+#define PCI_VENDOR_ID_MARVELL_EXT 0x1b4b
#define PCI_DEVICE_ID_MARVELL_GT64111 0x4146
#define PCI_DEVICE_ID_MARVELL_GT64260 0x6430
#define PCI_DEVICE_ID_MARVELL_MV64360 0x6460
next prev parent reply other threads:[~2013-03-21 4:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 4:34 [PATCH 0/3] PCI: Handle device quirks when accessing sysfs resource<N> entries Myron Stowe
2013-03-21 4:34 ` Myron Stowe [this message]
2013-03-21 4:35 ` [PATCH 2/3] " Myron Stowe
2013-03-22 0:51 ` Robert Hancock
2013-03-22 1:24 ` Greg KH
2013-03-22 15:39 ` Myron Stowe
2013-03-22 15:55 ` Robert Hancock
2013-03-22 16:46 ` Myron Stowe
2013-03-22 19:52 ` Elliott, Robert (Server Storage)
2013-04-04 18:06 ` Bjorn Helgaas
2013-04-06 8:49 ` James Bottomley
2013-04-08 17:29 ` Bjorn Helgaas
2013-03-21 4:35 ` [PATCH 3/3] PCI, scsi, ahci: Unify usages of 0x1b4b vendor ID to use PCI_VENDOR_ID_MARVELL_EXT Myron Stowe
2013-04-04 18:23 ` Bjorn Helgaas
2013-04-06 8:44 ` James Bottomley
2013-04-08 17:41 ` Bjorn Helgaas
2013-04-08 18:40 ` Jeff Garzik
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=20130321043456.7229.40987.stgit@amt.stowe \
--to=myron.stowe@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=greg@kroah.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=yuxiangl@marvell.com \
--cc=yxlraid@gmail.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).