public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Chou <thomas@wytron.com.tw>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org, nios2-dev@sopc.et.ntust.edu.tw,
	linux-input@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	Walter Goossens <waltergoossens@home.nl>,
	Tobias Klauser <klto@zhaw.ch>
Subject: Re: [PATCH v2] altera_ps2: Add devicetree support
Date: Thu, 03 Feb 2011 07:35:39 +0800	[thread overview]
Message-ID: <4D49EA4B.9000703@wytron.com.tw> (raw)
In-Reply-To: <20110202153959.GD20275@angua.secretlab.ca>

On 02/02/2011 11:39 PM, Grant Likely wrote:
> On Wed, Feb 02, 2011 at 07:48:58PM +0800, Thomas Chou wrote:
>> On 02/02/2011 12:31 PM, Grant Likely wrote:
>>>> +static const struct of_device_id altera_ps2_match[] = {
>>>> +	{ .compatible = "altr,ps2-1.0", },
>>>
>>> I thought I had seen 'altera' instead of an abbreviation being used in
>>> a previous patch.  I don't care much whether 'altr' or 'altera' is
>>> used, but I'd like to know that there is consensus from the Altera
>>> users so that all the drivers use the same prefix.
>>>
>>
>> We had discussed on nios2-dev mailing list, and decided to use
>> 'altr' as Walter suggested that it saves space.
>
> Is altr the stock ticker symbol?  The convention is to either use the
> stock ticker in all uppercase (although the uppercase bit hasn't been
> consistently applied), or to use the full name in lowercase.

Yes, it is the stock ticker symbol. Then we shall follow the convention, 
and change it to uppercase.

- Thomas

>
> g.
>
>


  reply	other threads:[~2011-02-02 23:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D040D1C.2020705@home.nl>
2011-01-17  6:29 ` [PATCH] alter_ps2: Add devicetree support Thomas Chou
2011-01-17  6:59   ` Grant Likely
2011-01-17 21:04     ` Walter Goossens
2011-01-17 22:02       ` Grant Likely
2011-01-17 23:27         ` Walter Goossens
2011-01-18 14:26           ` Thomas Chou
2011-01-17 21:31   ` Dmitry Torokhov
2011-01-17 22:04     ` Grant Likely
2011-01-24  5:58       ` [PATCH v2] altera_ps2: " Thomas Chou
2011-02-02  4:31         ` Grant Likely
2011-02-02  4:36           ` Grant Likely
2011-02-03  3:05             ` [PATCH v3] " Thomas Chou
2011-02-12  9:26               ` Grant Likely
2011-02-12 13:23                 ` Thomas Chou
2011-02-14  2:06                 ` [PATCH v4] " Thomas Chou
2011-02-14  2:20                   ` Dmitry Torokhov
2011-02-16  4:40                   ` Grant Likely
2011-02-02  4:45           ` [PATCH v2] " Dmitry Torokhov
2011-02-02 11:48           ` Thomas Chou
2011-02-02 12:11             ` [Nios2-dev] " Tobias Klauser
2011-02-02 15:38             ` Grant Likely
2011-02-02 23:32               ` Thomas Chou
2011-02-02 15:39             ` Grant Likely
2011-02-02 23:35               ` Thomas Chou [this message]
2011-02-03 22:27               ` Walter Goossens
2011-02-03 22:53                 ` Mitch Bradley
2011-02-03 23:02                   ` Walter Goossens

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=4D49EA4B.9000703@wytron.com.tw \
    --to=thomas@wytron.com.tw \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=klto@zhaw.ch \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nios2-dev@sopc.et.ntust.edu.tw \
    --cc=waltergoossens@home.nl \
    /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