From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] ARM: bcm281xx: Add GPIO driver
Date: Mon, 19 Aug 2013 20:11:50 +0100 [thread overview]
Message-ID: <2184179.Dja4tiYGvP@lenovo> (raw)
In-Reply-To: <CAPdLdqn31133KeQgFDcdN8jXDC5qbPn5HOS1mbfOMycMtgDkSg@mail.gmail.com>
Le lundi 19 ao?t 2013 12:05:55 Markus Mayer a ?crit :
> On 19 August 2013 12:02, Florian Fainelli <f.fainelli@gmail.com> wrote:
> > Hello Markus,
> >
> > Le lundi 19 ao?t 2013 11:59:19 Markus Mayer a ?crit :
> >> From: Markus Mayer <mmayer@broadcom.com>
> >>
> >> This patch adds the GPIO driver for the bcm281xx family of chips.
> >>
> >> Signed-off-by: Markus Mayer <markus.mayer@linaro.org>
> >> Reviewed-by: Christian Daudt <csd@broadcom.com>
> >> Reviewed-by: Tim Kryger <tim.kryger@linaro.org>
> >> Reviewed-by: Matt Porter <matt.porter@linaro.org>
> >> ---
> >>
> >> .../devicetree/bindings/gpio/gpio-bcm-kona.txt | 43 ++
> >
> > Since the vendor prefix has been changed from brcm to bcm, should that
> > also be reflected in the Device Tree binding documentation file?
>
> Actually, it is the other way around. "brcm," was there first, but we
> overlooked that and started upstreaming code with the "bcm," vendor
> prefix. There are various patches floating around out there to change
> our use of "bcm," to "brcm," to make it conform to the established
> vendor prefixes.
Ermm yes, I realized that after hitting send. Netherless, should this be
renamed to "gpio-brcm-kona.txt" directly such that the patches you mention do
not have to get updated to patch this one too?
--
Florian
next prev parent reply other threads:[~2013-08-19 19:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 18:59 [PATCH v4 0/3] ARM: bcm281xx: GPIO driver Markus Mayer
2013-08-19 18:59 ` [PATCH v4 1/3] ARM: bcm281xx: Add " Markus Mayer
2013-08-19 19:02 ` Florian Fainelli
2013-08-19 19:05 ` Markus Mayer
2013-08-19 19:11 ` Florian Fainelli [this message]
2013-08-19 19:23 ` Markus Mayer
2013-08-19 20:54 ` Florian Fainelli
2013-08-19 22:47 ` Tomasz Figa
2013-08-19 22:52 ` Stephen Warren
2013-08-19 22:50 ` Stephen Warren
2013-08-23 17:34 ` Linus Walleij
2013-08-23 17:58 ` Markus Mayer
2013-08-23 19:30 ` Markus Mayer
2013-08-28 19:50 ` Linus Walleij
2013-08-28 19:50 ` Linus Walleij
2013-08-19 18:59 ` [PATCH v4 2/3] ARM: bcm281xx: Enable " Markus Mayer
2013-08-23 17:37 ` Linus Walleij
2013-08-19 18:59 ` [PATCH v4 3/3] ARM: bcm281xx: Device Tree bindings for " Markus Mayer
2013-08-19 21:45 ` Tomasz Figa
2013-08-19 22:31 ` Markus Mayer
2013-08-23 17:38 ` Linus Walleij
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=2184179.Dja4tiYGvP@lenovo \
--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.