From: Greg KH <gregkh@linuxfoundation.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Joel Stanley <joel@jms.id.au>,
Eddie James <eajames@linux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-i2c@vger.kernel.org,
devicetree <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Jeremy Kerr <jk@ozlabs.org>,
Andrew Jeffery <andrew@aj.id.au>,
Christopher Bostic <cbostic@linux.vnet.ibm.com>,
"Edward A. James" <eajames@us.ibm.com>
Subject: Re: [PATCH v2 0/6] drivers/i2c: Add FSI-attached I2C master algorithm
Date: Mon, 17 Jul 2017 16:26:19 +0200 [thread overview]
Message-ID: <20170717142619.GA18850@kroah.com> (raw)
In-Reply-To: <20170717142013.ee2zzhlqx67bh7hr@ninjato>
On Mon, Jul 17, 2017 at 04:20:13PM +0200, Wolfram Sang wrote:
>
> > This is a driver for the i2c bus master, so I would expect the patches
> > to be reviewed and applied through Wolfram's i2c tree?
>
> Yes, please.
>
Ok, then why are people sending them to me?
I'll gladly let others take them :)
thanks,
greg k-h
prev parent reply other threads:[~2017-07-17 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 18:37 Eddie James
2017-07-10 18:37 ` [PATCH v2 1/6] " Eddie James
2017-07-10 18:37 ` [PATCH v2 2/6] drivers/i2c: Add port structure to FSI algorithm Eddie James
2017-07-10 18:37 ` [PATCH v2 3/6] drivers/i2c: Add transfer implementation for " Eddie James
2017-07-10 18:38 ` [PATCH v2 4/6] drivers/i2c: Add I2C master locking to " Eddie James
2017-07-10 18:38 ` [PATCH v2 5/6] drivers/i2c: Add bus recovery for " Eddie James
2017-07-10 18:38 ` [PATCH v2 6/6] dt-bindings: i2c: Add FSI-attached I2C master dt binding documentation Eddie James
2017-07-14 16:05 ` Rob Herring
2017-07-17 14:11 ` [PATCH v2 0/6] drivers/i2c: Add FSI-attached I2C master algorithm Greg KH
2017-07-17 14:16 ` Joel Stanley
2017-07-17 14:20 ` Wolfram Sang
2017-07-17 14:26 ` Greg KH [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=20170717142619.GA18850@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@aj.id.au \
--cc=cbostic@linux.vnet.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.vnet.ibm.com \
--cc=eajames@us.ibm.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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
Powered by JetHome