From: Alex Thorlton <athorlton@sgi.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Alex Thorlton <athorlton@sgi.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Hedi Berriche <hedi@sgi.com>,
x86@kernel.org
Subject: Re: [PATCH 1/2] Disable UV BAU by default
Date: Wed, 23 Mar 2016 12:25:16 -0500 [thread overview]
Message-ID: <20160323172516.GG205791@stormcage.americas.sgi.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1603231812500.3978@nanos>
On Wed, Mar 23, 2016 at 06:20:26PM +0100, Thomas Gleixner wrote:
> On Wed, 23 Mar 2016, Alex Thorlton wrote:
> > This was actually what I initially wrote, but we decided to go with the
> > on/off switch instead, because, in the UV4 time-frame, we're hoping to
> > get a few things changed so that we can default to having the bau *on*
> > for the new UV4 systems.
> >
> > I left that detail out of the original commit message, as I didn't
> > figure our future (still tentative) plans were all that important to the
> > community. I can add that information to my commit message, if you
> > would prefer to see it there.
>
> Yes please.
Got it. Will do.
> Please make that parameter boolean type, so you can just use strtobool().
>
> That supports "uvbau==[yYnN01]" and you can avoid the custom parser.
Makes sense. I'll get that taken care of.
Thanks again!
- Alex
next prev parent reply other threads:[~2016-03-23 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 17:04 [PATCH 0/2] Re-work UV BAU enable/disable logic, add documentation Alex Thorlton
2016-03-21 17:04 ` [PATCH 1/2] Disable UV BAU by default Alex Thorlton
2016-03-23 11:27 ` Thomas Gleixner
2016-03-23 16:11 ` Alex Thorlton
2016-03-23 17:20 ` Thomas Gleixner
2016-03-23 17:25 ` Alex Thorlton [this message]
2016-03-21 17:04 ` [PATCH 2/2] Add documentation for the bau parameter Alex Thorlton
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=20160323172516.GG205791@stormcage.americas.sgi.com \
--to=athorlton@sgi.com \
--cc=hedi@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®