netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@caviumnetworks.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Robert Richter <rric@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stefan Assmann <sassmann@redhat.com>,
	Sunil Goutham <sgoutham@cavium.com>,
	"David S. Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] VNIC: Adding support for Cavium ThunderX network controller
Date: Fri, 31 Oct 2014 17:17:24 +0100	[thread overview]
Message-ID: <20141031161724.GC31556@rric.localhost> (raw)
In-Reply-To: <20141030194513.089d27ec@urahara>

On 30.10.14 19:45:13, Stephen Hemminger wrote:
> On Thu, 30 Oct 2014 17:54:34 +0100
> Robert Richter <rric@kernel.org> wrote:
> 
> > diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> > index 1fa99a301817..80bd3336691e 100644
> > --- a/include/linux/pci_ids.h
> > +++ b/include/linux/pci_ids.h
> > @@ -2324,6 +2324,8 @@
> >  #define PCI_DEVICE_ID_ALTIMA_AC9100	0x03ea
> >  #define PCI_DEVICE_ID_ALTIMA_AC1003	0x03eb
> >  
> > +#define PCI_VENDOR_ID_CAVIUM		0x177d
> 
> I don't think PCI folks want this updated with every id anymore.

This is just the vendor id, the device id is part of the driver.

Since there will be multiple drivers I put the vendor id here.

-Robert

  reply	other threads:[~2014-10-31 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 16:54 [PATCH] VNIC: Adding support for Cavium ThunderX network controller Robert Richter
2014-10-31  2:45 ` Stephen Hemminger
2014-10-31 16:17   ` Robert Richter [this message]
2014-10-31  2:54 ` Stephen Hemminger
2014-10-31 17:14   ` Sunil Kovvuri
2014-11-03 18:16     ` Stephen Hemminger
2014-11-03 18:33       ` Robert Richter
2014-11-03 20:25         ` Stephen Hemminger

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=20141031161724.GC31556@rric.localhost \
    --to=robert.richter@caviumnetworks.com \
    --cc=davem@davemloft.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rric@kernel.org \
    --cc=sassmann@redhat.com \
    --cc=sgoutham@cavium.com \
    --cc=stephen@networkplumber.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).