From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, Wasim Khan <wasim.khan@nxp.com>,
Wei Fang <wei.fang@nxp.com>, Clark Wang <xiaoning.wang@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH pci] PCI: remove the PCI_VENDOR_ID_NXP alias
Date: Sun, 3 Dec 2023 17:15:03 +0200 [thread overview]
Message-ID: <20231203151503.vgyy7kidk7xhlles@skbuf> (raw)
In-Reply-To: <20231129233827.GA444332@bhelgaas>
On Wed, Nov 29, 2023 at 05:38:27PM -0600, Bjorn Helgaas wrote:
> Hmm. I can't find the 0x1957 Vendor ID here:
> https://pcisig.com/membership/member-companies which is supposed to
> be the authoritative source AFAICS.
>
> Also, that page lists 0x1131 as "NXP Semiconductors".
>
> There's a contact email on that page if it needs updates.
Sorry, I've no clue what's with that list of PCI SIG member companies.
Of course a company which no longer has a legal status cannot be a
member of the PCI SIG.
FWIW, the lspci tool uses this database: https://pci-ids.ucw.cz/
> I don't quite understand the goal here. The company is now called
> "NXP", and this patch removes PCI_VENDOR_ID_NXP (the only instance of
> "NXP" in pci_ids.h) and uses PCI_VENDOR_ID_FREESCALE (which apparently
> does not exist any more)?
>
> Why would we remove name of the current company and use the name of a
> company that doesn't exist any more?
Because that company doesn't produce new equipment with the old vendor id.
Aliasing the old vendor id to the current company name is polluting the
Linux definitions.
The goal, quite simply, is to call the Freescale PCI ID "Freescale".
prev parent reply other threads:[~2023-12-03 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 15:42 [PATCH pci] PCI: remove the PCI_VENDOR_ID_NXP alias Vladimir Oltean
2023-11-29 23:38 ` Bjorn Helgaas
2023-11-30 11:10 ` Greg Kroah-Hartman
2023-12-03 15:16 ` Vladimir Oltean
2023-12-03 17:30 ` Greg Kroah-Hartman
2023-12-03 17:48 ` Vladimir Oltean
2023-12-03 17:59 ` Greg Kroah-Hartman
2023-12-03 18:15 ` Vladimir Oltean
2023-12-03 15:15 ` Vladimir Oltean [this message]
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=20231203151503.vgyy7kidk7xhlles@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=wasim.khan@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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