From: Paul Clarke <pc@us.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/64s: dt_cpu_ftrs boot time setup option
Date: Fri, 12 May 2017 07:32:46 -0500 [thread overview]
Message-ID: <7f6307f3-6b5a-f655-a93c-3eb4bb1c2062@us.ibm.com> (raw)
In-Reply-To: <87inl6butu.fsf@concordia.ellerman.id.au>
On 05/11/2017 10:46 PM, Michael Ellerman wrote:
> Paul Clarke <pc@us.ibm.com> writes:
>> On 05/11/2017 06:24 AM, Nicholas Piggin wrote:
>>> Provide a dt_cpu_ftrs= cmdline option to disable the dt_cpu_ftrs CPU
>>> feature discovery, and fall back to the "cputable" based version.
>>
>> This boat has already sailed, I think, but "ftrs"?
>
> What you think vowels grow on trees! :)
At least you're using lower-case, which takes less space. ;-)
>> Was it too difficult to type "features"?
I see "ftrs" and think "footers".
> For the command line option we could spell out features.
>
> But should we also expand "dt", and "cpu" ?
>
> device_tree_central_processing_unit_features=off
I'm not the biggest fan of "dt" ("devtree", anyone?), but that's certainly established.
So _that's_ what "cpu" stands for! ;-)
> :P
>
>> This seems like something that should be easy and intuitive to find
>> and understand.
>
> Maybe. Ideally no one will ever use it, certainly not end users, it's
> primarily intended for developers doing bring-up.
I'm a developer, and I like to be able to understand something at a glance. (Hmm, what are "CPU footers"?)
:-P
PC
next prev parent reply other threads:[~2017-05-12 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 11:24 [PATCH] powerpc/64s: dt_cpu_ftrs boot time setup option Nicholas Piggin
2017-05-11 13:25 ` Paul Clarke
2017-05-12 3:46 ` Michael Ellerman
2017-05-12 12:32 ` Paul Clarke [this message]
2017-05-15 9:43 ` Michael Ellerman
2017-05-29 10:29 ` Michael Ellerman
2017-05-30 0:18 ` Nicholas Piggin
2017-05-30 5:32 ` Michael Ellerman
2017-05-29 22:29 ` Balbir Singh
2017-05-30 5:29 ` Michael Ellerman
2017-06-01 13:31 ` Michael Ellerman
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=7f6307f3-6b5a-f655-a93c-3eb4bb1c2062@us.ibm.com \
--to=pc@us.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
/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).