From: Matthew Wilcox <matthew@wil.cx>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
greg@kroah.com, linux-pci@vger.kernel.org,
isdn4linux@listserv.isdn4linux.de, kkeil@suse.de,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: CONFIG_PCI_LEGACY removal
Date: Fri, 21 Nov 2008 04:08:19 -0700 [thread overview]
Message-ID: <20081121110819.GA5707@parisc-linux.org> (raw)
In-Reply-To: <20081121181426.9f5efa36.sfr@canb.auug.org.au>
On Fri, Nov 21, 2008 at 06:14:26PM +1100, Stephen Rothwell wrote:
> Users of pci_find_device():
>
> drivers/isdn/hisax/avm_pci.c
> drivers/isdn/hisax/bkm_a4t.c
> drivers/isdn/hisax/bkm_a8.c
> drivers/isdn/hisax/diva.c
> drivers/isdn/hisax/elsa.c
> drivers/isdn/hisax/enternow_pci.c
> drivers/isdn/hisax/gazel.c
> drivers/isdn/hisax/hfc_pci.c
> drivers/isdn/hisax/niccy.c
> drivers/isdn/hisax/nj_s.c
> drivers/isdn/hisax/nj_u.c
> drivers/isdn/hisax/sedlbauer.c
> drivers/isdn/hisax/telespci.c
> drivers/isdn/hisax/w6692.c
I think the plan is to delete all these drivers once the new ISDN layer
is a bit more battle-hardened.
> User of pci_find_slot():
>
> drivers/pci/hotplug/cpqphp_pci.c
The cpqphp driver is basically unmaintained. Last time I spoke to Greg
about it (which was probably three years ago) he said it wasn't possible
to find a machine which had one of these any more.
I suspect the driver should simply be deleted, but if anyone steps up
and claims to have one of these to test the resulting patch, I'm willing
to remove pci_find_slot() from it.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-11-21 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 7:14 CONFIG_PCI_LEGACY removal Stephen Rothwell
2008-11-21 11:08 ` Matthew Wilcox [this message]
2008-11-21 16:21 ` Greg KH
2008-11-22 14:41 ` Alex Chiang
2008-11-21 11:13 ` 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=20081121110819.GA5707@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.