linux-kernel - Re: [2.6 patch] mark pci_find_device() as _

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:	Sun, 19 Nov 2006 15:13:04 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Alan Cox <alan@...hat.com>, Andrew Morton <akpm@...l.org>,
	gregkh@...e.de, linux-kernel@...r.kernel.org,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [2.6 patch] mark pci_find_device() as __deprecated

On Sun, 2006-11-19 at 15:04 +0100, Adrian Bunk wrote:
> On Sun, Nov 19, 2006 at 10:47:12AM +0100, Arjan van de Ven wrote:
> > 
> > > 
> > > Oh, and if anything starts complaining "But this adds some warnings to 
> > > my kernel build!", he should either first fix the 200 kB (sic) of 
> > > warnings I'm getting in 2.6.19-rc5-mm2 starting at MODPOST or go to hell.
> > 
> > we can solve this btw; we could have a
> > 
> > #define THIS_MODULE_IS_LEGACY_CRAP_AND_WONT_GET_FIXED
> >...
> 
> The few warnings by __deprecated are not that much of a problem.

yes they are; the current situation prevents things that are used in
only a set of old unmaintained legacy drivers (read: ISDN) as being
marked __deprecated because they add too many warnings, while the API
really should be marked deprecated..

think for example the entire sleep_on() family of API's (which basically
are impossible to use race-free in 2.6)





-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

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