On Mon, 16 Jun 2014, Doug Anderson wrote:
> From: Bill Richardson
>
> When communicating with the EC, the cmd_xfer() function should return the
> number of bytes it received from the EC, or negative on error.
>
> Signed-off-by: Bill Richardson
> Signed-off-by: Doug Anderson
> ---
> drivers/i
Hi Doug,
On 17 June 2014 21:54, Doug Anderson wrote:
> Simon,
>
> On Tue, Jun 17, 2014 at 8:46 PM, Simon Glass wrote:
>> Hi,
>>
>> On 16 June 2014 14:40, Doug Anderson wrote:
>>> From: Bill Richardson
>>>
>>> When communicating with the EC, the cmd_xfer() function should return the
>>> number
Simon,
On Tue, Jun 17, 2014 at 8:46 PM, Simon Glass wrote:
> Hi,
>
> On 16 June 2014 14:40, Doug Anderson wrote:
>> From: Bill Richardson
>>
>> When communicating with the EC, the cmd_xfer() function should return the
>> number of bytes it received from the EC, or negative on error.
>
> This is
Hi,
On 16 June 2014 14:40, Doug Anderson wrote:
> From: Bill Richardson
>
> When communicating with the EC, the cmd_xfer() function should return the
> number of bytes it received from the EC, or negative on error.
This is just for the I2C tunnel feature, right? If so, I think this
should be me
From: Bill Richardson
When communicating with the EC, the cmd_xfer() function should return the
number of bytes it received from the EC, or negative on error.
Signed-off-by: Bill Richardson
Signed-off-by: Doug Anderson
---
drivers/i2c/busses/i2c-cros-ec-tunnel.c | 2 +-
drivers/mfd/cros_ec_i2