From: Thomas Renninger <trenn@suse.de>
To: Jan Beulich <JBeulich@novell.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
Tejun Heo <tj@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH, resend] x86: unify "numa=" command line option handling
Date: Wed, 19 Jan 2011 10:19:21 +0100 [thread overview]
Message-ID: <201101191019.21299.trenn@suse.de> (raw)
In-Reply-To: <4D36B581020000780002D0FF@vpn.id2.novell.com>
On Wednesday, January 19, 2011 09:57:21 AM Jan Beulich wrote:
> In order to be able to suppress the use of SRAT tables that 32-bit
> Linux can't deal with (in one case known to lead to a non-bootable
> system, unless disabling ACPI altogether), move the "numa=" option
> handling to common code.
As this does not only unify the numa_32/64.c code a bit, but is
also needed for being able to boot a machine, it looks like a
candidate for 2.6.38-rcX.
Reviewed-by: Thomas Renninger <trenn@suse.de>
Thomas
prev parent reply other threads:[~2011-01-19 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 8:57 [PATCH, resend] x86: unify "numa=" command line option handling Jan Beulich
2011-01-19 9:19 ` Thomas Renninger [this message]
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=201101191019.21299.trenn@suse.de \
--to=trenn@suse.de \
--cc=JBeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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