···135 * Generic i2c master transfer entrypoint.136 *137 * Note: We do not use Atmel's feature of storing the "internal device address".138- * Instead the "internal device address" has to be written using a seperate139 * i2c message.140 * http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-September/024411.html141 */
···135 * Generic i2c master transfer entrypoint.136 *137 * Note: We do not use Atmel's feature of storing the "internal device address".138+ * Instead the "internal device address" has to be written using a separate139 * i2c message.140 * http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-September/024411.html141 */
+1-1
drivers/i2c/busses/i2c-powermac.c
···94 break;9596 /* Note that these are broken vs. the expected smbus API where97- * on reads, the lenght is actually returned from the function,98 * but I think the current API makes no sense and I don't want99 * any driver that I haven't verified for correctness to go100 * anywhere near a pmac i2c bus anyway ...
···94 break;9596 /* Note that these are broken vs. the expected smbus API where97+ * on reads, the length is actually returned from the function,98 * but I think the current API makes no sense and I don't want99 * any driver that I haven't verified for correctness to go100 * anywhere near a pmac i2c bus anyway ...
+1-1
drivers/i2c/i2c-dev.c
···184185/* This address checking function differs from the one in i2c-core186 in that it considers an address with a registered device, but no187- bounded driver, as NOT busy. */188static int i2cdev_check_addr(struct i2c_adapter *adapter, unsigned int addr)189{190 struct list_head *item;
···184185/* This address checking function differs from the one in i2c-core186 in that it considers an address with a registered device, but no187+ bound driver, as NOT busy. */188static int i2cdev_check_addr(struct i2c_adapter *adapter, unsigned int addr)189{190 struct list_head *item;