Re: [PATCH 1/2] i2c: mux: Use __i2c_transfer() instead of calling parent's master_xfer()

On Fri, Jun 12, 2015 at 02:40:37PM +0200, Alexander Sverdlin wrote: > Newly introduced quirks infrastructure doesn't work for the devices behind > MUXes because MUX's master_xfer() calls parent's master_xfer() directly > without checking the quirks. Instead of duplicating check code in MUX just > c

[PATCH 1/2] i2c: mux: Use __i2c_transfer() instead of calling parent's master_xfer()

Newly introduced quirks infrastructure doesn't work for the devices behind MUXes because MUX's master_xfer() calls parent's master_xfer() directly without checking the quirks. Instead of duplicating check code in MUX just call __i2c_transfer() instead. This has a side effect on tracing (messages wi