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: <1163929632.31358.481.camel@laptopd505.fenrus.org>
Date:	Sun, 19 Nov 2006 10:47:12 +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


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

(and yes the define should be really offensive so that nobody will put
it in a maintained module, and maybe it should even cause the kernel to
printk something when such a module gets loaded into the kernel)

If this sounds like a good idea I'll code it up...


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