linux-kernel - [PATCH 0/2] Remove __dev* sections from the kernel

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

Date:	Thu, 29 Nov 2012 10:41:33 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	linux-kernel@...r.kernel.org,
	Rusty Russell <rusty@...tcorp.com.au>,
	Jim Cromie <jim.cromie@...il.com>,
	Borislav Petkov <borislav.petkov@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <ak@...ux.intel.com>, Michal Marek <mmarek@...e.cz>,
	Tony Lindgren <tony@...mide.com>,
	Jonathan Kliegman <kliegs@...omium.org>,
	Chris Zankel <chris@...kel.net>
Cc:	Bill Pemberton <wfp5p@...idian.itc.virginia.edu>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Sam Ravnborg <sam@...nborg.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: [PATCH 0/2] Remove __dev* sections from the kernel

With the recent work to remove CONFIG_HOTPLUG, we are starting to get a
bunch of __devinit section warnings, despite CONFIG_HOTPLUG always being
enabled.  So lets remove these false warnings by removing the check for
them in the modpost.c tool.  Also, lets stop marking the sections
entirely, so define away the section markings in init.h

I'll queue these two patches up through my driver-core git tree, which
has the bulk of the __dev* marking removal patches in it.  If anyone has
any objections to this, please let me know.

thanks,

greg k-h

---
 include/linux/init.h  |   18 +++++++-----------
 scripts/mod/modpost.c |   24 ++++++++++--------------
 2 files changed, 17 insertions(+), 25 deletions(-)

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