From: Florian Fainelli <fainelli@broadcom.com>
To: Linus Walleij <linus.walleij@linaro.org>,
"Yendapally Reddy Dhananjaya Reddy" <yrdreddy@broadcom.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"Russell King" <linux@arm.linux.org.uk>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] ARM: dts: enable GPIO-a for Broadcom NSP
Date: Thu, 10 Dec 2015 16:33:36 -0800 [thread overview]
Message-ID: <566A19E0.5070803@broadcom.com> (raw)
In-Reply-To: <CACRpkdZ3ANXouYwFajnNOyPKZsXef6zdszLM525n9GVbUT2nOQ@mail.gmail.com>
On 10/12/15 09:46, Linus Walleij wrote:
> On Fri, Dec 4, 2015 at 6:12 PM, Yendapally Reddy Dhananjaya Reddy
> <yrdreddy@broadcom.com> wrote:
>
>> This enables the GPIO-a support for Broadcom NSP SoC
>>
>> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yrdreddy@broadcom.com>
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> Please merge this through the ARM SoC tree or BCM upstream tree,
> however that works.
The same way as any other ARM-based SoCs, so I will take this one. Thanks.
--
Florian
next prev parent reply other threads:[~2015-12-11 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 17:12 [PATCH v2 3/3] ARM: dts: enable GPIO-a for Broadcom NSP Yendapally Reddy Dhananjaya Reddy
2015-12-10 17:46 ` Linus Walleij
2015-12-11 0:33 ` Florian Fainelli [this message]
2016-02-11 20:01 ` Florian Fainelli
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=566A19E0.5070803@broadcom.com \
--to=fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jonmason@broadcom.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=yrdreddy@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).