On Thu, May 16, 2013 at 09:37:11PM +0100, Russell King wrote: > As this driver does not advertise protocol mangling support > (I2C_FUNC_PROTOCOL_MANGLING is not set), having code to act on > I2C_M_NOSTART is illogical, and in any case isn't supportable on > anything but the first message - which makes no sense. Remove > the I2C_M_NOSTART code. There is I2C_FUNC_NOSTART, though if it's only possible to use it on the first message that is pretty much useless as you say.
Attachment:
signature.asc
Description: Digital signature
