linux-kernel - Re: so what *is* obsolete and removable?

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 17 Apr 2007 16:33:37 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	Tilman Schmidt <tilman@...p.cc>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	"Robert P. J. Day" <rpjday@...dspring.com>,
	i4ldeveloper@...tserv.isdn4linux.de, Karsten Keil <kkeil@...e.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: so what *is* obsolete and removable?

On Tue, 17 Apr 2007 17:03:58 +0200
Tilman Schmidt <tilman@...p.cc> wrote:

> On Tue, 17 Apr 2007 14:40:54 +0100, Alan Cox wrote:
> > If the obsolete tag is to be removed then it needs a formal maintainer,
> > all the obsolete interface usage cleaning up and the like otherwise at
> > some point in a clean up it is going to end up breaking and migrating to
> > && BROKEN as well.
> 
> I'm not sure I understand. What do you mean by "obsolete interface
> usage"? What sort of cleaning up needs to be done? What sort of
> breakage do you anticipate in the event of a clean up?

Things like:

	pci_find_device
	pci_find_bus

	interruptible_sleep_on
	sleep_on

	lock_kernel
	unlock_kernel

and the drivers that i4l uses (eg hisax) need switching to the proper
pci_module interfaces to handle hot plug.

-
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/