All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid.aziz@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc64: Add ADI capability to cpu capabilities
Date: Wed, 16 Dec 2015 15:01:03 +0000	[thread overview]
Message-ID: <56717CAF.3090003@oracle.com> (raw)
In-Reply-To: <1449097600-23288-1-git-send-email-khalid.aziz@oracle.com>

On 12/15/2015 08:13 PM, David Miller wrote:
> From: Khalid Aziz <khalid.aziz@oracle.com>
> Date: Tue, 15 Dec 2015 17:25:42 -0700
>
>> adi is the externally visible name for this feature and that is how it
>> is referenced in the docs. Firmware encodes it as "adp" for its
>> internal use and that is how it shows up in hwcap-list property. So
>> this code translates it from firmware internal name to the external
>> name which would make sense to someone looking at /proc/cpuinfo.
>
> I totally disagree with changing the string.
>
> If the firmware provides X that's what we should publish in the
> cap list.  It doesn't really matter what the docs say.
>
> Otherwise we have this rediculous set of translations whenever
> something like this pops up again, and that kind of crud tends
> to accumulate.
>

It is a marketing/copyright thing, but I agree with you :) Let me check 
with marketing if they are ok with not doing the translation.

Thanks,
Khalid

  parent reply	other threads:[~2015-12-16 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 23:06 [PATCH] sparc64: Add ADI capability to cpu capabilities Khalid Aziz
2015-12-02 23:06 ` Khalid Aziz
2015-12-16  0:11 ` Josip Rodin
2015-12-16  0:25 ` Khalid Aziz
2015-12-16  3:13 ` David Miller
2015-12-16 15:01 ` Khalid Aziz [this message]
2015-12-16 16:06 ` David Miller

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=56717CAF.3090003@oracle.com \
    --to=khalid.aziz@oracle.com \
    --cc=sparclinux@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.