linux-kernel - Re: RFC: cleaning up the in-kernel headers

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, 16 Jul 2006 20:53:50 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Christoph Lameter <clameter@....com>
Cc:	Adrian Bunk <bunk@...sta.de>, linux-kernel@...r.kernel.org,
	David Woodhouse <dwmw2@...radead.org>, torvalds@...l.org,
	akpm@...l.org
Subject: Re: RFC: cleaning up the in-kernel headers

On Fri, 2006-07-14 at 21:59 -0700, Christoph Lameter wrote:

> > Now for the vmstat.h, I just tried removing that, and it seems that this
> > is a candidate to be removed from mm.h since mm.h compiles fine without
> > it. But vmstat.h doesn't compile without mm.h.  So it seems that we
> > should add mm.h to vmstat.h, remove vmstat.h from mm.h and for those .c
> > files that break, just add vmstat.h to them.
> 
> Great if you can detangle that.

Are you supporting the effort if I send in patches that removes the
vmstat.h and then goes and tries to find all the places that fail to
compile because of the removal and adds vmstat.h directly, that the
patches would get accepted?

It would probably need to go into -mm for a bit just to find those
places I missed.

This wouldn't be a problem to do and can be accomplished rather quickly,
but I wont waste any time on it if it is doomed at the start.

-- Steve

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