From: Michael Ellerman <mpe@ellerman•id.au>
To: pc@us•ibm.com, Nicholas Piggin <npiggin@gmail•com>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH] powerpc/64s: dt_cpu_ftrs boot time setup option
Date: Mon, 15 May 2017 19:43:08 +1000 [thread overview]
Message-ID: <87vap2a21f.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <7f6307f3-6b5a-f655-a93c-3eb4bb1c2062@us.ibm.com>
Paul Clarke <pc@us•ibm.com> writes:
> 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".
"FTR" - the shouty version - has meant "feature" in the powerpc code
base since at least 2002.
So it may be a crappy abbreviation but it's at least consistent :)
cheers
next prev parent reply other threads:[~2017-05-15 9:43 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
2017-05-15 9:43 ` Michael Ellerman [this message]
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=87vap2a21f.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
--cc=pc@us$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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