From: David Miller <davem@davemloft.net>
To: rmody@brocade.com
Cc: netdev@vger.kernel.org, adapter_linux_open_src_team@brocade.com,
gkaraje@brocade.com
Subject: Re: [net-next 4/7] bna: Brocade 1860 HW Enablement
Date: Tue, 27 Sep 2011 00:41:53 -0400 (EDT) [thread overview]
Message-ID: <20110927.004153.558055626011624681.davem@davemloft.net> (raw)
In-Reply-To: <1317071541-9662-5-git-send-email-rmody@brocade.com>
From: Rasesh Mody <rmody@brocade.com>
Date: Mon, 26 Sep 2011 14:12:18 -0700
> include/linux/pci_ids.h | 1 +
Please do not add new PCI device ID entries to linux/pci_ids.h
for use by a single device driver.
That header is only used when the PCI device ID will be used in
multiple drivers (such as network + iSCSI as some of the broadcom
drivers are).
next prev parent reply other threads:[~2011-09-27 4:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 21:12 [net-next 0/7] bna: H/W enablement and update driver version to 3.0.2.2 Rasesh Mody
2011-09-26 21:12 ` [net-next 1/7] bna: Brocade 1860 IOC PLL, Reg Defs and ASIC Mode Changes Rasesh Mody
2011-09-26 21:12 ` [net-next 2/7] bna: Capability Map and MFG Block Changes for New HW Rasesh Mody
2011-09-26 21:12 ` [net-next 3/7] bna: Implement FW Download " Rasesh Mody
2011-09-26 21:12 ` [net-next 4/7] bna: Brocade 1860 HW Enablement Rasesh Mody
2011-09-27 4:41 ` David Miller [this message]
2011-09-26 21:12 ` [net-next 5/7] bna: PLL Init Fix and Add Stats Attributes Rasesh Mody
2011-09-26 21:12 ` [net-next 6/7] bna: Add Callback to Fix RXQ Stop Rasesh Mody
2011-09-26 21:12 ` [net-next 7/7] bna: Driver Version changed to 3.0.2.2 Rasesh Mody
-- strict thread matches above, loose matches on Subject: below --
2011-09-27 20:39 [net-next 0/7] bna: H/W enablement and update driver version " Rasesh Mody
2011-09-27 20:39 ` [net-next 4/7] bna: Brocade 1860 HW Enablement Rasesh Mody
2011-09-24 2:14 [net-next 0/7] bna: H/W enablement and update driver version to 3.0.2.2 Rasesh Mody
2011-09-24 2:14 ` [net-next 4/7] bna: Brocade 1860 HW Enablement Rasesh Mody
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=20110927.004153.558055626011624681.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adapter_linux_open_src_team@brocade.com \
--cc=gkaraje@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.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).