linux-kernel - Re: [RFC/PULL 00/11] introduce export.h; reduce module.h usage

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: <20110728154229.GA19589@windriver.com>
Date:	Thu, 28 Jul 2011 11:42:29 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Ingo Molnar <mingo@...e.hu>, <sfr@...b.auug.org.au>
CC:	<torvalds@...ux-foundation.org>, <linux-kernel@...r.kernel.org>,
	<akpm@...ux-foundation.org>, <linux-arch@...r.kernel.org>
Subject: Re: [RFC/PULL 00/11] introduce export.h; reduce module.h usage

[Re: [RFC/PULL 00/11] introduce export.h; reduce module.h usage] On 28/07/2011 (Thu 09:15) Ingo Molnar wrote:

> 
> * Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
> 
> > I don't think there really is any rocket science or contentious 
> > stuff here. It is a sensible cleanup that adds organization and 
> > speeds up compiles. The RFC I'm hoping for is more about how/when 
> > we want to get this in tree.
> 
> I'd suggest to stick it into linux-next ASAP, leave there for a few 
> days and after fixing any potential fallout send it Linuswards.

Hi Stephen,

Would you please add this to linux-next?

git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git#module.h-split

It won't need to be there forever, just long enough to shake loose
anyone who has implicitly been using module.h without asking for it.

Thanks,
Paul.

> 
> Acked-by: Ingo Molnar <mingo@...e.hu>
> 
> Thanks,
> 
> 	Ingo
--
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/