All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-pci@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH] pci_ids: Remove old serial device IDs
Date: Thu, 24 Apr 2014 15:02:45 -0600	[thread overview]
Message-ID: <20140424210245.GF29593@google.com> (raw)
In-Reply-To: <20140331151929.7bd3afef@endymion.delvare>

On Mon, Mar 31, 2014 at 03:19:29PM +0200, Jean Delvare wrote:
> These IDs are no longer referenced since kernel 3.1 so I suppose we
> can remove them from pci_ids.h.
> 
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Cc: Bjorn Helgaas <bhelgaas@google.com>

Applied with Greg's ack to pci/misc for v3.16, thanks!

> ---
>  include/linux/pci_ids.h |    3 ---
>  1 file changed, 3 deletions(-)
> 
> --- linux-3.14-rc8.orig/include/linux/pci_ids.h	2014-03-31 14:15:00.832955000 +0200
> +++ linux-3.14-rc8/include/linux/pci_ids.h	2014-03-31 14:55:08.635085484 +0200
> @@ -1628,8 +1628,6 @@
>  #define PCI_DEVICE_ID_ATT_VENUS_MODEM	0x480
>  
>  #define PCI_VENDOR_ID_SPECIALIX		0x11cb
> -#define PCI_DEVICE_ID_SPECIALIX_IO8	0x2000
> -#define PCI_DEVICE_ID_SPECIALIX_RIO	0x8000
>  #define PCI_SUBDEVICE_ID_SPECIALIX_SPEED4 0xa004
>  
>  #define PCI_VENDOR_ID_ANALOG_DEVICES	0x11d4
> @@ -2868,7 +2866,6 @@
>  #define PCI_DEVICE_ID_SCALEMP_VSMP_CTL	0x1010
>  
>  #define PCI_VENDOR_ID_COMPUTONE		0x8e0e
> -#define PCI_DEVICE_ID_COMPUTONE_IP2EX	0x0291
>  #define PCI_DEVICE_ID_COMPUTONE_PG	0x0302
>  #define PCI_SUBVENDOR_ID_COMPUTONE	0x8e0e
>  #define PCI_SUBDEVICE_ID_COMPUTONE_PG4	0x0001
> 
> 
> -- 
> Jean Delvare
> SUSE L3 Support

      parent reply	other threads:[~2014-04-24 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 13:19 [PATCH] pci_ids: Remove old serial device IDs Jean Delvare
2014-04-16 20:15 ` Greg Kroah-Hartman
2014-04-24 21:02 ` Bjorn Helgaas [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=20140424210245.GF29593@google.com \
    --to=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.de \
    --cc=jslaby@suse.cz \
    --cc=linux-pci@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.