From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
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>
Subject: Re: [PATCH pci] PCI: remove the PCI_VENDOR_ID_NXP alias
Date: Sun, 3 Dec 2023 18:30:13 +0100 [thread overview]
Message-ID: <2023120354-expansion-frequency-f991@gregkh> (raw)
In-Reply-To: <20231203151654.nh4ta7vtzwpwg4ss@skbuf>
On Sun, Dec 03, 2023 at 05:16:54PM +0200, Vladimir Oltean wrote:
> On Thu, Nov 30, 2023 at 11:10:19AM +0000, Greg Kroah-Hartman wrote:
> > > Why would we remove name of the current company and use the name of a
> > > company that doesn't exist any more?
> >
> > Yes, this seems very odd. What is the reason for any of this other than
> > marketing? Kernel code doesn't do marketing :)
>
> I'm not sure who is doing the marketing; not me, that's for sure.
> The patch that I'm proposing undoes these strange aliases.
Why? Who did it originally in what commit id and what was wrong with
them then?
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-03 17:52 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 [this message]
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
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=2023120354-expansion-frequency-f991@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=vladimir.oltean@nxp.com \
--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