From: Myron Stowe <mstowe@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: myron.stowe@redhat.com, linux-pci@vger.kernel.org,
netdev@vger.kernel.org, bhelgaas@google.com, saeedm@mellanox.com,
noaos@mellanox.com, tariqt@mellanox.com
Subject: Re: [PATCH 0/2] Replace driver's usage of hard-coded device IDs to #defines
Date: Thu, 25 May 2017 09:56:55 -0600 [thread overview]
Message-ID: <20170525095655.3a577ea2@zim> (raw)
In-Reply-To: <20170524.200249.1492095559302424098.davem@davemloft.net>
On Wed, 24 May 2017 20:02:49 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Myron Stowe <myron.stowe@redhat.com>
> Date: Wed, 24 May 2017 16:47:34 -0600
>
> > 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).
>
> If you're adding pci_ids.h defines, it's only valid to do so if you
> actually use the defines in more than one location.
>
> This patch series is not doing that.
Hi David,
Yes, now that you mention that again I do vaguely remember past
conversations stating similar constraints which is a little odd as
Noa's series did exactly that. It was Bjorn, in a separate patch, that
made the connection to the driver with commit c19e4b9037f
("net/mlx4_core: Use device ID defines") [1] and even after such, some
of the introduced #defines are still currently singular in usage.
Anyway, the part I'm interested in is creating a more transparent
association between the Mellanox controllers that need the INTx masking
quirk and their drivers, something that remains very opaque currently
for a few of the remaining instances (PCI_DEVICE_ID_MELLANOX_CONNECTIB,
PCI_DEVICE_ID_MELLANOX_CONNECTX4, and
PCI_DEVICE_ID_MELLANOX_CONNECTX4_LX).
I'd like to hear back from others as to whether or not there is truly
concern about adding the #defines such as I submitted with singular
usages and if so I can re-submit a more focused patch which would
effectively be the first three substitutions in "[PATCH 2/2] net/mlx5e:
Use device ID defines".
[1] Perhaps Noa's submission had a similar discussion as while it was
a separate series from which Bjorn then made the connection to the
driver, all the patches came in via the same merge commit 25831571419
("Merge branch 'pci/virtualization' into next").
Thanks for your
feedback,
Myron
next prev parent reply other threads:[~2017-05-25 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 22:47 [PATCH 0/2] Replace driver's usage of hard-coded device IDs to #defines Myron Stowe
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 [this message]
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=20170525095655.3a577ea2@zim \
--to=mstowe@redhat.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=linux-pci@vger.kernel.org \
--cc=myron.stowe@redhat.com \
--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).