linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, Peter Chen <peter.chen@kernel.org>,
	Pawel Laszczak <pawell@cadence.com>,
	Roger Quadros <rogerq@kernel.org>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v1 1/1] usb: cdns3: Synchronise PCI IDs via common data base
Date: Wed, 13 Nov 2024 05:53:56 +0100	[thread overview]
Message-ID: <2024111345-recall-party-e801@gregkh> (raw)
In-Reply-To: <20241112212447.GA1861184@bhelgaas>

On Tue, Nov 12, 2024 at 03:24:47PM -0600, Bjorn Helgaas wrote:
> On Tue, Nov 12, 2024 at 06:01:25PM +0200, Andy Shevchenko wrote:
> > There are a few places in the kernel where PCI IDs for different Cadence
> > USB controllers are being used. Besides different naming, they duplicate
> > each other. Make this all in order by providing common definitions via
> > PCI IDs database and use in all users. While doing that, rename
> > definitions as Roger suggested.
> > 
> > Suggested-by: Roger Quadros <rogerq@kernel.org>
> > Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> 
> Looks like maybe something for the USB tree?

Sure, I'll take it, thanks!

greg k-h

      reply	other threads:[~2024-11-13  4:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 16:01 [PATCH v1 1/1] usb: cdns3: Synchronise PCI IDs via common data base Andy Shevchenko
2024-11-12 21:24 ` Bjorn Helgaas
2024-11-13  4:53   ` Greg Kroah-Hartman [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=2024111345-recall-party-e801@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=fenghua.yu@intel.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=pawell@cadence.com \
    --cc=peter.chen@kernel.org \
    --cc=rogerq@kernel.org \
    /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).