Re: [PATCH v6 1/4] i2c: add a protocol parameter to the alert callback

2016-03-19 Thread Andrew Duggan
On Wed, Mar 16, 2016 at 9:39 AM, Benjamin Tissoires wrote: > .alert() is meant to be generic, but there is currently no way > for the device driver to know which protocol generated the alert. > Add a parameter in .alert() to help the device driver to understand > what is given in data. > > This pa

Re: [PATCH v6 1/4] i2c: add a protocol parameter to the alert callback

2016-03-19 Thread Corey Minyard
Looks ok to me. For IPMI: Acked-by: Corey Minyard On 03/16/2016 11:39 AM, Benjamin Tissoires wrote: .alert() is meant to be generic, but there is currently no way for the device driver to know which protocol generated the alert. Add a parameter in .alert() to help the device driver to underst

Re: [PATCH v6 1/4] i2c: add a protocol parameter to the alert callback

2016-03-18 Thread Guenter Roeck
On Wed, Mar 16, 2016 at 05:39:05PM +0100, Benjamin Tissoires wrote: > .alert() is meant to be generic, but there is currently no way > for the device driver to know which protocol generated the alert. > Add a parameter in .alert() to help the device driver to understand > what is given in data. >

[PATCH v6 1/4] i2c: add a protocol parameter to the alert callback

2016-03-18 Thread Benjamin Tissoires
.alert() is meant to be generic, but there is currently no way for the device driver to know which protocol generated the alert. Add a parameter in .alert() to help the device driver to understand what is given in data. This patch is required to have the support of SMBus Host Notify protocol throu