From: Grant Coady <gcoady@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci_ids: remove non-referenced symbols from pci_ids.h
Date: Mon, 31 Oct 2005 14:38:13 +1100 [thread overview]
Message-ID: <436591A5.20609@gmail.com> (raw)
In-Reply-To: <20051031024217.GA25709@redhat.com>
Dave Jones wrote:
> On Fri, Oct 28, 2005 at 05:00:11PM -0700, Linux Kernel wrote:
> > tree 68609a74c3bc43e510f58f9c808a0a74e9d23452
> > parent 4153812fc10ea91cb1a7b6ea4f4337dd211c1ef7
> > author Grant Coady <gcoady@gmail.com> Thu, 29 Sep 2005 11:06:40 +1000
> > committer Greg Kroah-Hartman <gregkh@suse.de> Sat, 29 Oct 2005 05:36:59 -0700
> >
> > [PATCH] pci_ids: remove non-referenced symbols from pci_ids.h
> >
> > pci_ids.h cleanup: removed non-referenced symbols, compile tested
> > with 'make allmodconfig'
> >
> > Signed-off-by: Grant Coady <gcoady@gmail.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> This patch is removing some PCI idents from drivers that are currently
> marked BROKEN on some/all architectures. It seems counterproductive
> to create even more work to get those drivers fixed.
Nobody cares, the drivers are dying of bit-rot :)
> Especially in the case of for eg, the advansys scsi driver, which
> actually works for some people, even though it isn't updated to use
> modern scsi layer interfaces.
Any positive suggestions? How many years does a driver remain
broken before it gets removed? These drivers don't compile cleanly
thus are not in use, no? Perhaps a set of patches scheduling
removal is in order.
Grant.
next prev parent reply other threads:[~2005-10-31 3:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200510290000.j9T00Bqd001135@hera.kernel.org>
2005-10-31 2:42 ` [PATCH] pci_ids: remove non-referenced symbols from pci_ids.h Dave Jones
2005-10-31 3:38 ` Grant Coady [this message]
2005-10-31 4:13 ` Dave Jones
2005-10-31 5:26 ` Grant Coady
2005-10-31 5:56 ` Dave Jones
2005-10-31 15:45 ` Alan Cox
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=436591A5.20609@gmail.com \
--to=gcoady@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@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