linux-kernel - Re: CONFIG_PCI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20081122144159.GH25709@ldl.fc.hp.com>
Date:	Sat, 22 Nov 2008 07:41:59 -0700
From:	Alex Chiang <achiang@...com>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	LKML <linux-kernel@...r.kernel.org>, greg@...ah.com,
	linux-pci@...r.kernel.org, isdn4linux@...tserv.isdn4linux.de,
	kkeil@...e.de, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: CONFIG_PCI_LEGACY removal

* Matthew Wilcox <matthew@....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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/