From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andi@firstfloor.org" <andi@firstfloor.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] [arch-x86] Allow SRAT integrity check to be skipped
Date: Thu, 02 Sep 2010 12:39:00 -0700 [thread overview]
Message-ID: <1283456340.28591.23.camel@pjaxe> (raw)
In-Reply-To: <1283427192.3793.100.camel@jlt3.sipsolutions.net>
On Thu, 2010-09-02 at 04:33 -0700, Johannes Berg wrote:
> On Wed, 2010-09-01 at 15:59 -0700, Peter P Waskiewicz Jr wrote:
>
> > +static int srat_bypass_bios;
> > +
> > +static int __init srat_bypass_bios_setup(char *str)
> > +{
> > + srat_bypass_bios = 1;
> > + return 0;
> > +}
> > +early_param("sratbypassbios", srat_bypass_bios_setup);
> > +
> > /* Use the information discovered above to actually set up the nodes. */
> > int __init acpi_scan_nodes(unsigned long start, unsigned long end)
> > {
>
> I wonder, since all the things using the variable are __init, could it
> be as well? Just curious really.
That is a good question. It makes sense to me, but I just followed what
other boot-time options did, which are not marked __init. I'll defer to
anyone else on the list who is better-equipped to answer that.
-PJ
prev parent reply other threads:[~2010-09-02 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 22:59 [PATCH v2] [arch-x86] Allow SRAT integrity check to be skipped Peter P Waskiewicz Jr
2010-09-02 11:33 ` Johannes Berg
2010-09-02 19:39 ` Peter P Waskiewicz Jr [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=1283456340.28591.23.camel@pjaxe \
--to=peter.p.waskiewicz.jr@intel.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).