From: Florian Fainelli <f.fainelli@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>, Florian Fainelli <f.fainelli@gmail.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
Wei Xu <xuwei5@hisilicon.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Riku Voipio <riku.voipio@linaro.org>,
Thierry Reding <treding@nvidia.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Eric Anholt <eric@anholt.net>,
Magnus Damm <damm+renesas@opensource.se>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: defconfig: Enable ARCH_BRCMSTB
Date: Thu, 8 Jun 2017 13:46:41 -0700 [thread overview]
Message-ID: <647c565a-9207-b108-265e-2259530752c0@gmail.com> (raw)
In-Reply-To: <CAK8P3a3zT0bh=itVjwWTEJFwoBxeQgpRZWJRhg8=Rk9-iyE04g@mail.gmail.com>
On 06/07/2017 12:50 PM, Arnd Bergmann wrote:
> On Wed, Jun 7, 2017 at 6:58 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> ARCH_BRCMSTB was one of the few platforms that were not enabled by
>> default, since we are now adding more and more drivers relevant to that
>> platform get some proper build coverage.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> I can submit this through the next arm-soc pull requests (shortly), if
>> that's okay with all of you, thanks!
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
Applied to defconfig-arm64/next, thanks!
--
Florian
prev parent reply other threads:[~2017-06-08 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 16:58 Florian Fainelli
2017-06-07 19:50 ` Arnd Bergmann
2017-06-08 20:46 ` Florian Fainelli [this message]
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=647c565a-9207-b108-265e-2259530752c0@gmail.com \
--to=f.fainelli@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=damm+renesas@opensource.se \
--cc=eric@anholt.net \
--cc=gregory.clement@free-electrons.com \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.voipio@linaro.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.com \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®