public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Matt Mackall <mpm@selenic.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Andi Kleen <ak@suse.de>, Ingo Molnar <mingo@elte.hu>,
	Arjan van de Ven <arjan@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RFC, Announce] Unified x86 architecture, arch/x86
Date: Sun, 22 Jul 2007 09:50:46 +0200	[thread overview]
Message-ID: <1185090646.4012.149.camel@chaos> (raw)
In-Reply-To: <20070721235109.GQ3672@sequoia.sous-sol.org>

On Sat, 2007-07-21 at 16:51 -0700, Chris Wright wrote:
> * Matt Mackall (mpm@selenic.com) wrote:
> > Can we see some stats on:
> > 
> > How many files were auto-merged?
> > How many files got 32.c and 64.c extensions?
> > How many existed only in one arch?
> 
> It's mostly about file movement first.
> 
>  918 files changed, 4745 insertions(+), 2836 deletions(-)

Hmm, did you forget to make distclean ?

Numbers from the script:

include/asm-i386     240 files
include/asm-x86_64   169 files
------------------------------
                     409 files

include/asm-x86      389 files

arch/i386            335 files
arch/x86_64          141 files
------------------------------
                     476 files

arch/x86             484 files

The increase here is due to migration helper files which only include
the (_32.x or the _64.x) variant.

Makefile helpers       9 files
Kconfig helpers        1 file
Source helpers         4 files
------------------------------
                      14 files

Summary:
vanilla            22657 files
vanilla->x86       22649 files

------------------------------

include/x86 has 125 _32 and 125 _64 files
arch/x86 has     55 _32 and  55 _64 files

25 files were auto-merged

Looking at include/asm-x86/*_[32/64].h there are offhand ~ 50 of the 125
which differ only minimal (white space damage, comment changes, ...),
where the unification is a no brainer.

	tglx



  reply	other threads:[~2007-07-22  7:50 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 22:32 [RFC, Announce] Unified x86 architecture, arch/x86 Thomas Gleixner
2007-07-20 22:38 ` Jeff Garzik
2007-07-20 22:40   ` Ingo Molnar
2007-07-20 22:42     ` Jeff Garzik
2007-07-20 22:51       ` Linus Torvalds
2007-07-21  2:56     ` Yinghai Lu
2007-07-20 23:55   ` Alan Cox
2007-07-21  0:02     ` H. Peter Anvin
2007-07-21 22:26     ` Oleg Verych
2007-07-20 23:01 ` Arjan van de Ven
2007-07-20 23:23   ` Steven Rostedt
2007-07-21  2:39     ` Glauber de Oliveira Costa
2007-07-20 23:55 ` Michal Piotrowski
2007-07-21  0:03   ` Ingo Molnar
2007-07-21  0:16     ` Michal Piotrowski
2007-07-21  5:40   ` Andi Kleen
2007-07-21  5:50     ` Steven Rostedt
2007-07-21  6:06       ` Andi Kleen
2007-07-21  7:35         ` Adrian Bunk
2007-07-21  7:42           ` Andi Kleen
2007-07-21  8:01             ` Adrian Bunk
2007-07-21  8:15             ` Thomas Gleixner
2007-07-21  8:32             ` Ingo Molnar
2007-07-27 10:50         ` Pavel Machek
2007-07-27 18:11           ` Chris Wright
2007-07-20 23:55 ` Arnd Bergmann
2007-07-21  1:59   ` Steven Rostedt
2007-07-21  1:01 ` Gabriel C
2007-07-21  5:37 ` Andi Kleen
2007-07-21  5:58   ` Steven Rostedt
2007-07-21  6:09     ` Andi Kleen
2007-07-21  8:15   ` Thomas Gleixner
2007-07-21  8:28     ` Andi Kleen
2007-07-21 13:28       ` Glauber de Oliveira Costa
2007-07-21  9:02     ` Rusty Russell
2007-07-21 11:34     ` Brian Gerst
2007-07-21 12:30       ` Ingo Molnar
2007-07-21 15:11   ` Arjan van de Ven
2007-07-21  6:37 ` Avi Kivity
2007-07-21 10:37 ` David Woodhouse
2007-07-21 10:56 ` Adrian Bunk
2007-07-21 22:25 ` Matt Mackall
2007-07-21 23:51   ` Chris Wright
2007-07-22  7:50     ` Thomas Gleixner [this message]
2007-07-22 12:02       ` Matt Mackall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1185090646.4012.149.camel@chaos \
    --to=tglx@linutronix.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mpm@selenic.com \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox