From: Thomas Gleixner <tglx@linutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>, 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 22:44:42 +0200 [thread overview]
Message-ID: <1189457082.25767.58.camel@chaos> (raw)
In-Reply-To: <20070910203445.GA32047@uranus.ravnborg.org>
Sam,
On Mon, 2007-09-10 at 22:34 +0200, Sam Ravnborg wrote:
> Partly so. Took a look at the x86 tree.
> The main Makefile are at least not merged. Neither are pci/Makefile not
> boot/compressed/Makefile.
Yeah I know. Those are the non trivial ones and the boot/compressed one
might be split forever. The pci Makefile has link order problems
(initcall order wreckage) and the main Makefile as well. Needs more
thought.
> And some of the rest of the Makefiles are not pretty with the huge arch
> specific sections ifdeffed out.
I completely agree.
> -ifneq ($(CONFIG_ACPI_PROCESSOR),)
> -obj-y += cstate.o processor.o
> -endif
> +obj-$(CONFIG_X86_32)-if-$(CONFIG_ACPI_SLEEP) += sleep_32.o wakeup_32.o
> +obj-$(CONFIG_X86_64)-if-$(CONFIG_ACPI_SLEEP) += sleep_64.o wakeup_64.o
> +
> +obj-y-if-$(CONFIG_ACPI_PROCESSOR) += cstate.o processor.o
>
>
> My biggest worry is that we end up with a more compact format
> but only me (and a very few others) can read it.
> But I think the above could make the x86 Makefiles more readable
> as a whole.
It's way better than the ifneq(...) stuff and completely understandable
at least for me. I'd like to see that change, it is helpful on a bunch
of other places in the kernel as well.
Thanks,
tglx
next prev parent reply other threads:[~2007-09-10 20:44 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
2007-09-10 20:34 ` Sam Ravnborg
2007-09-10 20:44 ` Thomas Gleixner [this message]
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=1189457082.25767.58.camel@chaos \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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