From: Len Brown <lenb@kernel.org>
To: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: Alexey Starikovskiy <astarikovskiy@suse.de>,
Andi Kleen <ak@suse.de>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: mpparse_{32,64}.c merge questions
Date: Tue, 11 Mar 2008 13:28:43 -0400 [thread overview]
Message-ID: <200803111328.43314.lenb@kernel.org> (raw)
In-Reply-To: <20080304213552.GD8944@elte.hu>
On Tuesday 04 March 2008, Ingo Molnar wrote:
>
> (more folks Cc:-ed)
>
> * Alexey Starikovskiy <astarikovskiy@suse.de> wrote:
>
> >>> I've decided to start with merge of mpparse files, and I'd like to
> >>> know your opinion on some differences... Ingo, I know you work on
> >>> merging the 32/64 files, do I step on your toes?
> >>
> >> My suggestion would be to do a redesign first and then do that for
> >> both.
> > I was thinking that redesign on one file would go easier... And we
> > don't need both, do we?
>
> we dont, but please do _not_ "redesign" anything during unification.
>
> try to keep it simple and bisectable. Lots of small patches. Stupid
> #ifdefs if need to be. Pick the 32-bit version or the 64-bit version of
> any approach, if it's obvious that the unified version will still work
> fine. Ask if in doubt.
I agree with Ingo on the "keep it simple" merge steps..
I can't resist mentioning, however, what I'd like to see long term.
I'd like to see mpparse.o depend on CONFIG_MPS=y
I'd like to be able to build CONFIG_ACPI=y and CONFIG_MPS=n
Andy Grover prototyped splititing MPS from ACPI a while back,
but it never made it upstream.
thanks,
-Len
next parent reply other threads:[~2008-03-11 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47CDB9D7.9030107@suse.de>
[not found] ` <47CDBFD9.1050703@suse.de>
[not found] ` <20080304213552.GD8944@elte.hu>
2008-03-11 17:28 ` Len Brown [this message]
2008-03-11 17:34 ` mpparse_{32,64}.c merge questions Alexey Starikovskiy
2008-03-12 7:04 ` Ingo Molnar
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=200803111328.43314.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=ak@suse.de \
--cc=astarikovskiy@suse.de \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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