From: Alex Chiang <achiang@hp.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Sat, 22 Nov 2008 07:41:59 -0700 [thread overview]
Message-ID: <20081122144159.GH25709@ldl.fc.hp.com> (raw)
In-Reply-To: <20081121110819.GA5707@parisc-linux.org>
* Matthew Wilcox <matthew@wil.cx>:
> On Fri, Nov 21, 2008 at 06:14:26PM +1100, Stephen Rothwell wrote:
>
> 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've managed to track some down.
> 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.
Converting cpqphp to use the modern pci_get_slot() API has been
on my TODO list for a while. It was languishing because I
couldn't find hardware nor time.
I've got hardware now. Just need to free up a few cycles. :-/
But if it's not worth it, I'm fine with marking as CONFIG_BROKEN
and scheduling for eventual deletion.
/ac
next prev parent reply other threads:[~2008-11-22 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 7:14 Stephen Rothwell
2008-11-21 11:08 ` Matthew Wilcox
2008-11-21 16:21 ` Greg KH
2008-11-22 14:41 ` Alex Chiang [this message]
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=20081122144159.GH25709@ldl.fc.hp.com \
--to=achiang@hp.com \
--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=matthew@wil.cx \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®