From: Wolfram Sang <wsa@the-dreams.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org, kdasu.kdev@gmail.com,
geert@linux-m68k.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Jean Delvare <jdelvare@suse.de>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Karthikeyan Ramasubramanian <kramasub@codeaurora.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Eddie James <eajames@linux.vnet.ibm.com>,
James Hogan <jhogan@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"open list:I2C SUBSYSTEM HOST DRIVERS"
<linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v2] i2c: brcmstb: Allow enabling the driver on DSL SoCs
Date: Fri, 5 Oct 2018 14:07:27 +0200 [thread overview]
Message-ID: <20181005120727.GE5433@kunai> (raw)
In-Reply-To: <20181001174349.26357-1-f.fainelli@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
On Mon, Oct 01, 2018 at 10:43:47AM -0700, Florian Fainelli wrote:
> ARCH_BCM_63XX which is used by ARM-based DSL SoCs from Broadcom uses the
> same controller, make it possible to select the STB driver and update
> the Kconfig and help text a bit.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> Changes in v2:
>
> - Make COMPILE_TEST last, as per Geert's recommendation
>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-10-05 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 17:43 [PATCH v2] i2c: brcmstb: Allow enabling the driver on DSL SoCs Florian Fainelli
2018-10-01 18:13 ` Andy Shevchenko
2018-10-02 10:22 ` Arnd Bergmann
2018-10-02 10:27 ` Andy Shevchenko
2018-10-05 12:07 ` Wolfram Sang [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=20181005120727.GE5433@kunai \
--to=wsa@the-dreams.de \
--cc=andy.shevchenko@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=eajames@linux.vnet.ibm.com \
--cc=f.fainelli@gmail.com \
--cc=geert@linux-m68k.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=jhogan@kernel.org \
--cc=kdasu.kdev@gmail.com \
--cc=kramasub@codeaurora.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=wsa+renesas@sang-engineering.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).