From: Ingo Molnar <mingo@elte.hu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sam Ravnborg <sam@ravnborg.org>, Andi Kleen <ak@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
kbuild devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [RFC] kbuild - introduce vdir to make life easier for x86_64
Date: Mon, 10 Sep 2007 21:29:20 +0200 [thread overview]
Message-ID: <20070910192920.GA2080@elte.hu> (raw)
In-Reply-To: <1189452121.25767.42.camel@chaos>
* Thomas Gleixner <tglx@linutronix.de> wrote:
> On Mon, 2007-09-10 at 21:11 +0200, Sam Ravnborg wrote:
> > One of the complaints raised about the current x86_64 Makfiles are
> > the ugliness needed to reuse code from i386. Andi asked me if we
> > could do something in kbuild to make this less ugly and below are
> > the hack I could come up with.
>
> while in general this is definitely a nice change, it does not really
> solve the real problem of code scattered across two architectures. The
> Makefile polishing is the least thing we care about.
>
> Thanks,
i'd like to add it here that Makefile polishing is important - it's just
that in the context of arch/*x86* the Makefile impact of the current
cross-arch code sharing practice is one of the smaller problems and the
Makefiles get cleaned up via the arch/x86 merge anyway.
Ingo
next prev parent reply other threads:[~2007-09-10 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 19:11 [RFC] kbuild - introduce vdir to make life easier for x86_64 Sam Ravnborg
2007-09-10 19:22 ` Thomas Gleixner
2007-09-10 19:29 ` Ingo Molnar [this message]
2007-09-10 20:34 ` Sam Ravnborg
2007-09-10 20:44 ` Thomas Gleixner
2007-09-10 22:40 ` Andi Kleen
2007-09-10 22:50 ` H. Peter Anvin
2007-09-11 6:49 ` Sam Ravnborg
2007-09-11 19:42 ` 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=20070910192920.GA2080@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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