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]

Message-Id: <1163930476.31358.483.camel@laptopd505.fenrus.org>
Date:	Sun, 19 Nov 2006 11:01:16 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Muli Ben-Yehuda <muli@...ibm.com>
Cc:	Adrian Bunk <bunk@...sta.de>, 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 11:52 +0200, Muli Ben-Yehuda 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
> > 
> > that would turn __deprecated into a nop for those few legacy modules
> > inside the kernel that nobody really is looking after.
> 
> If no one is looking after them, shouldn't they just be removed?


that's a whole different flamewar, esp if they sort of kinda mostly work
if the moon is aligned properly with Mars.


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