linux-kernel - Re: [GIT PULL] x86: use arch/x86/include

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: <20080730184700.GA29710@uranus.ravnborg.org>
Date:	Wed, 30 Jul 2008 20:47:00 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Jeff Dike <jdike@...toit.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [GIT PULL] x86: use arch/x86/include

On Wed, Jul 30, 2008 at 08:04:11PM +0200, Ingo Molnar wrote:
> 
> * Sam Ravnborg <sam@...nborg.org> wrote:
> 
> > Hi x86 guys.
> > 
> > It turned out to be easy to enable um to use arch/x86/include so here 
> > is a git pull.
> 
> hm, we have a _ton_ of changes to include files queued up already, so 
> this is rather inconvenient.
git should cope with this if changes come in via git. I do not
know about "git am" applied patches.

> 
> I missed the discussion on this, what's the point of renaming all these 
> files?

It has been discussed many times to keep arch and arch include files
under arch/.
Lately Linus outlined this:

    http://kerneltrap.org/mailarchive/linux-kernel/2008/5/21/1903924

I took the ball and did the kbuild side of this so we could do this
gradually.
sparc are already converted. sh has it ready to be pulled and others
are playing with it.

How we do it in the best way for such a fragile codebase as x86 is
I am not sure. I would assume to do it late in the merge window where
the minimum set of patches are queued up would be best (and this is now).

And Linus already said he would like to take it sooner.
Quote:

====================================================================
On Tue, 29 Jul 2008, Sam Ravnborg wrote:
>
> But will you accept this stuff now or will we have to wait until
> next merge window?

if the patches are really small adn the resulting build is well tested
(ignoring the actual _move_ operation), I'm ok with taking them.

In fact, in many ways I'd _prefer_ to do it now, rather than have it
pending and then do it durign the next merge window when there are a lot
of non-movement changes too.
====================================================================

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