linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Kamal Dasu <kdasu.kdev@gmail.com>,
	Jean Delvare <jdelvare@suse.de>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Vignesh R <vigneshr@ti.com>,
	Eddie James <eajames@linux.vnet.ibm.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Ajay Gupta <ajayg@nvidia.com>,
	Karthikeyan Ramasubramanian <kramasub@codeaurora.org>,
	Juergen Fitschen <jfi@ssv-embedded.de>,
	Elie Morisse <syniurge@gmail.com>,
	"open list:I2C SUBSYSTEM HOST DRIVERS"
	<linux-i2c@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: Allow selecting BCM2835 I2C controllers on ARCH_BRCMSTB
Date: Mon, 27 May 2019 21:21:56 +0200	[thread overview]
Message-ID: <20190527192156.GF8808@kunai> (raw)
In-Reply-To: <20190509210438.28223-1-f.fainelli@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 383 bytes --]

On Thu, May 09, 2019 at 02:04:36PM -0700, Florian Fainelli wrote:
> From: Kamal Dasu <kdasu.kdev@gmail.com>
> 
> ARCH_BRCMSTB platforms have the BCM2835 I2C controllers, allow
> selecting the i2c-bcm2835 driver on such platforms.
> 
> Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>

Applied to for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2019-05-27 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 21:04 [PATCH] i2c: Allow selecting BCM2835 I2C controllers on ARCH_BRCMSTB Florian Fainelli
2019-05-10  8:12 ` Jean Delvare
2019-05-27 19:21 ` 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=20190527192156.GF8808@kunai \
    --to=wsa@the-dreams.de \
    --cc=ajayg@nvidia.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=eajames@linux.vnet.ibm.com \
    --cc=f.fainelli@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jdelvare@suse.de \
    --cc=jfi@ssv-embedded.de \
    --cc=kdasu.kdev@gmail.com \
    --cc=kramasub@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syniurge@gmail.com \
    --cc=vigneshr@ti.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).