[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACPK8XfeMLA5vUEkxVO_U=rN49gvGZ4zfdBJbxX44yTiUy27yw@mail.gmail.com>
Date: Mon, 17 Jul 2017 23:46:18 +0930
From: Joel Stanley <joel@....id.au>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Eddie James <eajames@...ux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-i2c@...r.kernel.org, devicetree <devicetree@...r.kernel.org>,
Wolfram Sang <wsa@...-dreams.de>,
Rob Herring <robh+dt@...nel.org>, Jeremy Kerr <jk@...abs.org>,
Andrew Jeffery <andrew@...id.au>,
Christopher Bostic <cbostic@...ux.vnet.ibm.com>,
"Edward A. James" <eajames@...ibm.com>
Subject: Re: [PATCH v2 0/6] drivers/i2c: Add FSI-attached I2C master algorithm
On Mon, Jul 17, 2017 at 11:41 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> On Mon, Jul 10, 2017 at 01:37:56PM -0500, Eddie James wrote:
>> From: "Edward A. James" <eajames@...ibm.com>
>>
>> This series adds an algorithm for an I2C master physically located on an FSI
>> slave device. The I2C master has multiple ports, each of which may be connected
>> to an I2C slave. Access to the I2C master registers is achieved over FSI bus.
>>
>> Due to the multi-port nature of the I2C master, the driver instantiates a new
>> I2C adapter for each port connected to a slave. The connected ports should be
>> defined in the device tree under the I2C master device.
>>
>> Changes since v1:
>
> I have 2 "v2" series in my inbox, and they are different :(
>
> Please resend a "v4" so I know exactly which ones to pick up...
Hi Greg,
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?
Eddie, regardless can you please send a v4 so we know which version to
be reviewing.
Cheers,
Joel
Powered by blists - more mailing lists