All of lore.kernel.org
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] MAINTAINERS: add entry for the Broadcom Northstar Plus SoCs
Date: Wed, 26 Aug 2015 10:17:05 -0700	[thread overview]
Message-ID: <55DDF491.3090700@gmail.com> (raw)
In-Reply-To: <CAOesGMioBQY9qy-S8kMJmo_=B6-KZiUkd=Ns1Uo2dGu0BiqppQ@mail.gmail.com>

On 25/08/15 16:42, Olof Johansson wrote:
> On Thu, Aug 20, 2015 at 10:47 AM, Jon Mason <jonmason@broadcom.com> wrote:
>> Modify the iProc MAINTAINER to cover the Nortstar Plus SoCs, and add me
>> to the list of people responsible for it.
> 
> That's not what this patch does. It removes CYGNUS from the
> description as well. Hmm?
> 
> I'm also not a fan of the complex patterns, but that's more of a
> bikeshedding comment. Does Broadcom really not have a bit more
> systematic naming than this? :)

The naming conventions are fairly simple actually:

* BCM is just a common prefix for internal names/projects/whatever
* 9 indicates that this is a development/reference board
* 4 to 5 digits designate the chip identifier

Now, if you are trying to get some sense about how the chip ids are
actually chosen, I am afraid none of us have that knowledge ;)

> 
>> Signed-off-by: Jon Mason <jonmason@broadcom.com>
>> Reviewed-by: Scott Branden <sbranden@broadcom.com>
> 
> For maintainer updates, we usuallu like to see a public ack of this
> and not just a pre-acked patch. You _could_ have added it yourself
> without Scott's actual approval, after all.
> 
> 
> -Olof
> 


-- 
Florian

  reply	other threads:[~2015-08-26 17:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 17:47 [PATCH 5/5] MAINTAINERS: add entry for the Broadcom Northstar Plus SoCs Jon Mason
2015-08-25 23:42 ` Olof Johansson
2015-08-26 17:17   ` Florian Fainelli [this message]
2015-08-26 18:20   ` Scott Branden
2015-08-26 19:00   ` Jon Mason
2015-08-26 20:02     ` Olof Johansson

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=55DDF491.3090700@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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.