From: Andi Kleen <ak@suse.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86 merge - a little feedback
Date: Tue, 11 Sep 2007 22:34:23 +0100 [thread overview]
Message-ID: <200709112234.24155.ak@suse.de> (raw)
In-Reply-To: <20070911211422.GU3563@stusta.de>
>
> People do not expect code under arch/i386/ to be used by code under
> arch/x86_64/ and vice versa.
>
> That regularly results in people sending patches that don't compile on
> the other architecture.
>
> With one architecture it's much more obvious that the code is shared.
Will that cause people to compile test both? I have my doubts that
will really work.
e.g. a similar example would be CONFIG_MMU=n. The code
is mostly shared and in the same directories, but people still
break the MMUless architectures all the time.
I don't expect this to be different with 32bit/64bit.
-Andi
next prev parent reply other threads:[~2007-09-11 21:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 20:12 x86 merge - a little feedback Sam Ravnborg
2007-09-11 20:25 ` Thomas Gleixner
2007-09-11 21:24 ` Linus Torvalds
2007-09-11 20:34 ` Adrian Bunk
2007-09-11 21:05 ` Sam Ravnborg
2007-09-11 21:09 ` Adrian Bunk
2007-09-12 9:27 ` Christoph Hellwig
2007-09-12 12:45 ` Lennart Sorensen
2007-09-11 20:38 ` Andi Kleen
2007-09-11 21:14 ` Adrian Bunk
2007-09-11 21:34 ` Andi Kleen [this message]
2007-09-11 21:51 ` Linus Torvalds
2007-09-12 18:14 ` Jan Engelhardt
2007-09-11 21:51 ` Adrian Bunk
2007-09-12 0:29 ` Paul Mundt
2007-09-15 10:55 ` Andrew Morton
2007-09-15 9:32 ` Andrew Morton
2007-09-15 18:36 ` Andi Kleen
2007-09-16 5:08 ` Andrew Morton
2007-09-11 21:21 ` Linus Torvalds
2007-09-12 19:09 ` Sam Ravnborg
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=200709112234.24155.ak@suse.de \
--to=ak@suse.de \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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