linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Lee <adam.lee@canonical.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-pci@vger.kernel.org, linux-serial@vger.kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 1/2] pci_ids: Add Pericom vendor and device ids
Date: Mon, 3 Aug 2015 12:44:28 +0800	[thread overview]
Message-ID: <20150803044428.GD19820@adam-laptop> (raw)
In-Reply-To: <20150803043647.GA20605@kroah.com>

On Sun, Aug 02, 2015 at 09:36:47PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Aug 03, 2015 at 12:33:20PM +0800, Adam Lee wrote:
> > This patch add Pericom's vendor id and Pericom PI7C9X795[1248] chips'
> > device ids.
> > 
> > Signed-off-by: Adam Lee <adam.lee@canonical.com>
> > ---
> >  include/linux/pci_ids.h | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> > index fcff8f8..c4a93cf 100644
> > --- a/include/linux/pci_ids.h
> > +++ b/include/linux/pci_ids.h
> > @@ -2995,4 +2995,10 @@
> >  
> >  #define PCI_VENDOR_ID_OCZ		0x1b85
> >  
> > +#define PCI_VENDOR_ID_PERICOM			0x12D8
> > +#define PCI_DEVICE_ID_PERICOM_PI7C9X7951	0x7951
> > +#define PCI_DEVICE_ID_PERICOM_PI7C9X7952	0x7952
> > +#define PCI_DEVICE_ID_PERICOM_PI7C9X7954	0x7954
> > +#define PCI_DEVICE_ID_PERICOM_PI7C9X7958	0x7958
> 
> Please read the top of this file, this isn't needed...
> 
> thanks,
> 
> greg k-h

Oops. Pericom also has other products than serial card, so is it OK if I
still leave PCI_VENDOR_ID_PERICOM in pci_ids.h and move device ids to
particular driver? Thanks.

-- 
Adam Lee

  reply	other threads:[~2015-08-03  4:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03  4:33 [PATCH 1/2] pci_ids: Add Pericom vendor and device ids Adam Lee
2015-08-03  4:33 ` [PATCH 2/2] serial: 8250_pci: Add support for Pericom PI7C9X795[1248] Adam Lee
2015-08-03  4:36 ` [PATCH 1/2] pci_ids: Add Pericom vendor and device ids Greg Kroah-Hartman
2015-08-03  4:44   ` Adam Lee [this message]
2015-08-03  5:14     ` Greg Kroah-Hartman

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=20150803044428.GD19820@adam-laptop \
    --to=adam.lee@canonical.com \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-serial@vger.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).