From: Scott Branden <sbranden@broadcom.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: devicetree@vger.kernel.org,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Kevin Cernekee" <cernekee@gmail.com>,
"Corneliu Doban" <cdoban@broadcom.com>,
"Ray Jui" <rjui@broadcom.com>, "Rafał Miłecki" <zajec5@gmail.com>,
linux-kernel@vger.kernel.org,
"Jonathan Richardson" <jonathar@broadcom.com>,
"Anatol Pomazao" <anatol@google.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-mtd@lists.infradead.org,
"Dmitry Torokhov" <dtor@google.com>
Subject: Re: [PATCH 2/3] Documentation: devicetree: add binding doc for Broadcom NAND controller
Date: Mon, 16 Mar 2015 16:52:01 -0700 [thread overview]
Message-ID: <55076CA1.60007@broadcom.com> (raw)
In-Reply-To: <20150316234634.GN32500@ld-irv-0074>
Hi Brian,
On 15-03-16 04:46 PM, Brian Norris wrote:
> On Mon, Mar 16, 2015 at 04:40:13PM -0700, Scott Branden wrote:
>>
>> On 15-03-16 04:37 PM, Brian Norris wrote:
>>> On Mon, Mar 16, 2015 at 04:07:51PM -0700, Scott Branden wrote:
>>> So, what's the standard? Company prefix? Long name? Commas? Hyphens?
>>
>> The problem with devicetree binding is there is no standard for much
>> of anything. Some others use the vendor prefix for all their
>> binding documentation. We can try to do the same?
>
> Ok, but we already have 3 versions for Broadcom. I can use 'brcm,' if
> that helps...
Yes, it helps if we try standardizing on the brcm vendor prefix in
Documentation/devicetree/bindings/vendor-prefixes.txt. If you sift
through the bindings directory you will find some of the other vendors
have done the same.
Also, of note.
In Documentation/devicetree/bindings/submitting-patches.txt
it states the Documentation should be the first patch in the series.
Perhaps this helps the devicetree maintainer in reviewing bindings?
Scott
>
> Brian
>
WARNING: multiple messages have this Message-ID (diff)
From: Scott Branden <sbranden-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: Brian Norris <computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
"Dmitry Torokhov" <dtor-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"Anatol Pomazao" <anatol-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"Ray Jui" <rjui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
"Corneliu Doban" <cdoban-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
"Jonathan Richardson"
<jonathar-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
"Florian Fainelli"
<f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Rafał Miłecki" <zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Kevin Cernekee"
<cernekee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 2/3] Documentation: devicetree: add binding doc for Broadcom NAND controller
Date: Mon, 16 Mar 2015 16:52:01 -0700 [thread overview]
Message-ID: <55076CA1.60007@broadcom.com> (raw)
In-Reply-To: <20150316234634.GN32500@ld-irv-0074>
Hi Brian,
On 15-03-16 04:46 PM, Brian Norris wrote:
> On Mon, Mar 16, 2015 at 04:40:13PM -0700, Scott Branden wrote:
>>
>> On 15-03-16 04:37 PM, Brian Norris wrote:
>>> On Mon, Mar 16, 2015 at 04:07:51PM -0700, Scott Branden wrote:
>>> So, what's the standard? Company prefix? Long name? Commas? Hyphens?
>>
>> The problem with devicetree binding is there is no standard for much
>> of anything. Some others use the vendor prefix for all their
>> binding documentation. We can try to do the same?
>
> Ok, but we already have 3 versions for Broadcom. I can use 'brcm,' if
> that helps...
Yes, it helps if we try standardizing on the brcm vendor prefix in
Documentation/devicetree/bindings/vendor-prefixes.txt. If you sift
through the bindings directory you will find some of the other vendors
have done the same.
Also, of note.
In Documentation/devicetree/bindings/submitting-patches.txt
it states the Documentation should be the first patch in the series.
Perhaps this helps the devicetree maintainer in reviewing bindings?
Scott
>
> Brian
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Scott Branden <sbranden@broadcom.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org,
"Dmitry Torokhov" <dtor@google.com>,
"Anatol Pomazao" <anatol@google.com>,
"Ray Jui" <rjui@broadcom.com>,
"Corneliu Doban" <cdoban@broadcom.com>,
"Jonathan Richardson" <jonathar@broadcom.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Kevin Cernekee" <cernekee@gmail.com>
Subject: Re: [PATCH 2/3] Documentation: devicetree: add binding doc for Broadcom NAND controller
Date: Mon, 16 Mar 2015 16:52:01 -0700 [thread overview]
Message-ID: <55076CA1.60007@broadcom.com> (raw)
In-Reply-To: <20150316234634.GN32500@ld-irv-0074>
Hi Brian,
On 15-03-16 04:46 PM, Brian Norris wrote:
> On Mon, Mar 16, 2015 at 04:40:13PM -0700, Scott Branden wrote:
>>
>> On 15-03-16 04:37 PM, Brian Norris wrote:
>>> On Mon, Mar 16, 2015 at 04:07:51PM -0700, Scott Branden wrote:
>>> So, what's the standard? Company prefix? Long name? Commas? Hyphens?
>>
>> The problem with devicetree binding is there is no standard for much
>> of anything. Some others use the vendor prefix for all their
>> binding documentation. We can try to do the same?
>
> Ok, but we already have 3 versions for Broadcom. I can use 'brcm,' if
> that helps...
Yes, it helps if we try standardizing on the brcm vendor prefix in
Documentation/devicetree/bindings/vendor-prefixes.txt. If you sift
through the bindings directory you will find some of the other vendors
have done the same.
Also, of note.
In Documentation/devicetree/bindings/submitting-patches.txt
it states the Documentation should be the first patch in the series.
Perhaps this helps the devicetree maintainer in reviewing bindings?
Scott
>
> Brian
>
next prev parent reply other threads:[~2015-03-16 23:52 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 1:18 [PATCH 0/3] mtd: nand: add Broadcom NAND controller support Brian Norris
2015-03-07 1:18 ` Brian Norris
2015-03-07 1:18 ` Brian Norris
2015-03-07 1:18 ` [PATCH 1/3] mtd: nand: add common DT init code Brian Norris
2015-03-07 1:18 ` Brian Norris
2015-03-07 1:18 ` Brian Norris
2015-03-07 1:18 ` [PATCH 2/3] Documentation: devicetree: add binding doc for Broadcom NAND controller Brian Norris
2015-03-07 1:18 ` Brian Norris
2015-03-07 1:18 ` Brian Norris
2015-03-16 18:49 ` Florian Fainelli
2015-03-16 18:49 ` Florian Fainelli
2015-03-16 23:07 ` Scott Branden
2015-03-16 23:07 ` Scott Branden
2015-03-16 23:07 ` Scott Branden
2015-03-16 23:37 ` Brian Norris
2015-03-16 23:37 ` Brian Norris
2015-03-16 23:37 ` Brian Norris
2015-03-16 23:40 ` Scott Branden
2015-03-16 23:40 ` Scott Branden
2015-03-16 23:40 ` Scott Branden
2015-03-16 23:46 ` Brian Norris
2015-03-16 23:46 ` Brian Norris
2015-03-16 23:52 ` Scott Branden [this message]
2015-03-16 23:52 ` Scott Branden
2015-03-16 23:52 ` Scott Branden
2015-03-07 1:18 ` [PATCH 3/3] mtd: nand: add NAND driver for Broadcom STB " Brian Norris
2015-03-07 1:18 ` Brian Norris
2015-03-07 1:18 ` Brian Norris
2015-03-07 12:39 ` Paul Bolle
2015-03-07 12:39 ` Paul Bolle
2015-03-09 17:30 ` Brian Norris
2015-03-09 17:30 ` Brian Norris
2015-03-07 13:21 ` Rafał Miłecki
2015-03-07 13:21 ` Rafał Miłecki
2015-03-07 13:21 ` Rafał Miłecki
2015-03-09 17:31 ` Brian Norris
2015-03-09 17:31 ` Brian Norris
2015-03-07 17:39 ` Rafał Miłecki
2015-03-07 17:39 ` Rafał Miłecki
2015-03-07 21:48 ` Rafał Miłecki
2015-03-07 21:48 ` Rafał Miłecki
2015-03-07 21:48 ` Rafał Miłecki
2015-03-08 0:44 ` Rafał Miłecki
2015-03-08 0:44 ` Rafał Miłecki
2015-03-09 17:49 ` Brian Norris
2015-03-09 17:49 ` Brian Norris
2015-03-09 17:57 ` Ray Jui
2015-03-09 17:57 ` Ray Jui
2015-03-09 17:57 ` Ray Jui
2015-03-07 22:15 ` Rafał Miłecki
2015-03-07 22:15 ` Rafał Miłecki
2015-03-07 22:15 ` Rafał Miłecki
2015-03-16 18:55 ` Florian Fainelli
2015-03-16 18:55 ` Florian Fainelli
2015-03-16 18:55 ` Florian Fainelli
2015-03-19 1:49 ` Brian Norris
2015-03-19 1:49 ` Brian Norris
2015-03-16 19:58 ` Florian Fainelli
2015-03-16 19:58 ` Florian Fainelli
2015-03-08 0:01 ` [PATCH 0/3] mtd: nand: add Broadcom NAND controller support Rafał Miłecki
2015-03-08 0:01 ` Rafał Miłecki
2015-03-08 0:57 ` Brian Norris
2015-03-08 0:57 ` Brian Norris
2015-03-08 10:22 ` Rafał Miłecki
2015-03-08 10:22 ` Rafał Miłecki
2015-03-09 18:04 ` Brian Norris
2015-03-09 18:04 ` Brian Norris
2015-03-08 11:18 ` Rafał Miłecki
2015-03-08 11:18 ` Rafał Miłecki
2015-03-08 11:18 ` Rafał Miłecki
2015-03-09 17:59 ` Brian Norris
2015-03-09 17:59 ` Brian Norris
[not found] ` <CALj_zD5rW3Se27Rh0pL6QTMNGOrrmrvAVLvW3BCuF8RujYQE=g@mail.gmail.com>
2015-03-16 23:44 ` Brian Norris
2015-03-16 23:44 ` Brian Norris
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=55076CA1.60007@broadcom.com \
--to=sbranden@broadcom.com \
--cc=anatol@google.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=cdoban@broadcom.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dtor@google.com \
--cc=f.fainelli@gmail.com \
--cc=jonathar@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=zajec5@gmail.com \
/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.