public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>, Jeff Garzik <jgarzik@pobox.com>,
	Kieran Morrissey <linux@mgpenguin.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.1: Update PCI Name database, fix gen-devlist.c for long device names.
Date: Mon, 19 Jan 2004 17:29:56 -0800	[thread overview]
Message-ID: <20040120012956.GF6309@kroah.com> (raw)
In-Reply-To: <20040116042500.GA3658@redhat.com>

On Fri, Jan 16, 2004 at 04:25:00AM +0000, Dave Jones wrote:
> On Thu, Jan 15, 2004 at 05:23:14PM -0800, Greg KH wrote:
> 
>  > > Well, appreciated, but we really do need to remove it.  We don't need 
>  > > these strings in the kernel at all.  pci.ids is just a static lookup 
>  > > table that is best kept in userspace.
>  > 
>  > It will be removed in 2.7.
> 
> So I'm the only one with deja vu ?
> 
> My recollection of history went something like..
> 
> 2.2 - Marked as OBSOLETE when /proc/bus/pci came to town.
>       iirc, even Martin Mares (PCI maintainer at the time) wanted
> 	  it removed in 2.3.x
> 2.3 - Linus decides he likes it, and wants to keep it.
> 2.4 - Unmarked OBSOLETE
> 2.5 - Silence, (though we now get PCI stuff in /sys too, woo!)

No, we tried in 2.5 too.  Linus said it wanted to keep it as a CONFIG
option for now, so we can drop it in 2.7.

> 2.6 - "It will be removed in 2.7"
> 
> Anyone else spot a pattern ?  8-)

Heh, well, we can try again :)

thanks,

greg k-h

  reply	other threads:[~2004-01-20  1:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  3:28 [PATCH] 2.6.1: Update PCI Name database, fix gen-devlist.c for long device names Kieran Morrissey
2004-01-15  4:05 ` Jeff Garzik
2004-01-15  9:17   ` Ingo Oeser
2004-01-16  1:23   ` Greg KH
2004-01-16  4:25     ` Dave Jones
2004-01-20  1:29       ` Greg KH [this message]
2004-01-16  1:24 ` Greg KH
2004-01-17 10:39 ` Martin Mares
2004-01-20  1:30   ` Greg KH
2004-01-20  5:07     ` Kieran Morrissey

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=20040120012956.GF6309@kroah.com \
    --to=greg@kroah.com \
    --cc=davej@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@mgpenguin.net \
    /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