public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: moore@free•fr (Chris Moore)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: kirkwood: DT board setup for CloudBox
Date: Fri, 05 Apr 2013 07:14:17 +0200	[thread overview]
Message-ID: <515E5DA9.1000605@free.fr> (raw)
In-Reply-To: <20130405011143.GX13280@titan.lakedaemon.net>

Le 05/04/2013 03:11, Jason Cooper a ?crit :
> On Thu, Apr 04, 2013 at 11:34:35AM +0200, Simon Guinot wrote:
>>
...

>> Then we are back to the initial problem...
>>
>> Maybe we could append some suffixes based on the version:
>>
>> 1: cloudbox-v1
>> 2: cloudbox-v2
>>
>> Or better, suffix based on the other code names:
>>
>> 1: cloudbox-ns2mini
>> 2: cloudbox-familybox
>>
>> Or even let the things as they are:
>>
>> 1: netspace_v2_mini
>> 2: cloudbox
> In light of the above info, let's got with the third option.  If we
> discover a different LaCie Cloudbox board down the road, we can add an
> appropriately more specific compatible string to differentiate.  As you
> can tell, I'd prefer to have something more specific in the original
> commit, but we can only work with what we're given. :(
>

This is now OK with me.
However I would like to have a more precise description somewhere; 
probably either in the Kconfig or, if this is obsolescent, in whatever 
replaces it.
I think that someone grepping the kernel sources for the commercial name 
"CloudBox" should find both versions and be able to decide which one he has.

Cheers,
Chris

  reply	other threads:[~2013-04-05  5:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 11:06 [PATCH] ARM: kirkwood: DT board setup for CloudBox Simon Guinot
2013-03-29 15:31 ` Jason Cooper
2013-03-29 18:41   ` Simon Guinot
2013-03-30  6:51     ` Chris Moore
2013-03-30 15:08       ` Jason Cooper
2013-04-01 16:44         ` Simon Guinot
2013-04-01 16:33       ` Simon Guinot
2013-04-02  4:17         ` Chris Moore
2013-04-02 11:04           ` Simon Guinot
2013-04-02 11:45           ` Jason Cooper
2013-04-02 12:54             ` Simon Guinot
2013-04-02 17:24               ` Jason Cooper
2013-04-04  4:54                 ` Chris Moore
2013-04-04  8:00                   ` Simon Guinot
2013-04-04  9:34                     ` Simon Guinot
2013-04-05  1:11                       ` Jason Cooper
2013-04-05  5:14                         ` Chris Moore [this message]
2013-04-08 17:00                           ` Jason Cooper
2013-03-29 17:09 ` Andrew Lunn
2013-03-29 18:51   ` Simon Guinot

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=515E5DA9.1000605@free.fr \
    --to=moore@free$(echo .)fr \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /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