From: Myron Stowe <myron.stowe@redhat.com>
To: linux-pci@vger.kernel.org, netdev@vger.kernel.org
Cc: bhelgaas@google.com, saeedm@mellanox.com, noaos@mellanox.com,
tariqt@mellanox.com
Subject: [PATCH 0/2] Replace driver's usage of hard-coded device IDs to #defines
Date: Wed, 24 May 2017 16:47:34 -0600 [thread overview]
Message-ID: <20170524224734.24221.33787.stgit@amt.stowe> (raw)
Noa Osherovich introduced a series of new Mellanox device ID definitions to
help differentiate specific controllers that needed INTx masking quirks [1].
Bjorn Helgaas followed on, using the device ID definitions Noa provided to
replace hard-coded values within the mxl4 ID table [2].
This patch continues along similar lines, adding a few additional Mellanox
device ID definitions and converting the net/mlx5e driver's mlx5 ID table to
use the defines so tools like 'grep' and 'cscope' can be used to help
identify relationships with other aspects (such as INTx masking).
[1] 7254383341b PCI: Add Mellanox device IDs
d76d2fe05fd PCI: Convert Mellanox broken INTx quirks to be for listed
devices only
[2] c19e4b9037f net/mlx4_core: Use device ID defines
Myron Stowe (2):
PCI: Add Mellanox device IDs
net/mlx5e: Use device ID defines
drivers/net/ethernet/mellanox/mlx5/core/main.c | 12 ++++++------
include/linux/pci_ids.h | 3 +++
2 files changed, 9 insertions(+), 6 deletions(-)
--
next reply other threads:[~2017-05-24 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 22:47 Myron Stowe [this message]
2017-05-24 22:47 ` [PATCH 1/2] PCI: Add Mellanox device IDs Myron Stowe
2017-05-24 22:47 ` [PATCH 2/2] net/mlx5e: Use device ID defines Myron Stowe
2017-05-25 0:02 ` [PATCH 0/2] Replace driver's usage of hard-coded device IDs to #defines David Miller
2017-05-25 15:56 ` Myron Stowe
2017-06-16 20:08 ` Bjorn Helgaas
2017-06-16 20:21 ` Myron Stowe
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=20170524224734.24221.33787.stgit@amt.stowe \
--to=myron.stowe@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noaos@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.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).