Re: [PATCHv6 08/11] i2c: match vendorless strings on the internal string length

2016-11-01 Thread Lee Jones
On Mon, 31 Oct 2016, Kieran Bingham wrote: > On 31/10/16 13:55, Peter Rosin wrote: > > On 2016-10-26 10:53, Lee Jones wrote: > >> On Tue, 25 Oct 2016, Kieran Bingham wrote: > >> > >>> If a user provides a shortened string to match a device to the sysfs i2c > >>> interface it will match on the first

Re: [PATCHv6 08/11] i2c: match vendorless strings on the internal string length

2016-10-31 Thread Kieran Bingham
Hi Peter, Thanks for your review On 31/10/16 13:55, Peter Rosin wrote: > On 2016-10-26 10:53, Lee Jones wrote: >> On Tue, 25 Oct 2016, Kieran Bingham wrote: >> >>> If a user provides a shortened string to match a device to the sysfs i2c >>> interface it will match on the first string that contain

Re: [PATCHv6 08/11] i2c: match vendorless strings on the internal string length

2016-10-31 Thread Peter Rosin
On 2016-10-26 10:53, Lee Jones wrote: > On Tue, 25 Oct 2016, Kieran Bingham wrote: > >> If a user provides a shortened string to match a device to the sysfs i2c >> interface it will match on the first string that contains that string >> prefix. >> >> for example: >> echo a 0x68 > /sys/bus/i2c/de

Re: [PATCHv6 08/11] i2c: match vendorless strings on the internal string length

2016-10-26 Thread Lee Jones
On Tue, 25 Oct 2016, Kieran Bingham wrote: > If a user provides a shortened string to match a device to the sysfs i2c > interface it will match on the first string that contains that string > prefix. > > for example: > echo a 0x68 > /sys/bus/i2c/devices/i2c-2/new_device > > will match as3711,

[PATCHv6 08/11] i2c: match vendorless strings on the internal string length

2016-10-25 Thread Kieran Bingham
If a user provides a shortened string to match a device to the sysfs i2c interface it will match on the first string that contains that string prefix. for example: echo a 0x68 > /sys/bus/i2c/devices/i2c-2/new_device will match as3711, as3722, and ak8975 incorrectly. Signed-off-by: Kieran Bingh