Hi!

Many users of the i2c_mux_add_adapter interface log a message
on failure, but the function already logs such a message. One
or two of those users actually add more information than already
provided by the central failure message.

So, first fix the central error reporting to provide as much
information as any current user, and then remove the surplus
error reporting at the call sites.

Cheers,
peda

Peter Rosin (9):
  i2c: mux: provide more info on failure in i2c_mux_add_adapter
  i2c: arb: gpio-challenge: stop double error reporting
  i2c: mux: gpio: stop double error reporting
  i2c: mux: pca9541: stop double error reporting
  i2c: mux: pca954x: stop double error reporting
  i2c: mux: pinctrl: stop double error reporting
  i2c: mux: reg: stop double error reporting
  iio: gyro: mpu3050: stop double error reporting
  [media] cx231xx: stop double error reporting

 drivers/i2c/i2c-mux.c                      |  9 ++++++---
 drivers/i2c/muxes/i2c-arb-gpio-challenge.c |  4 +---
 drivers/i2c/muxes/i2c-mux-gpio.c           |  4 +---
 drivers/i2c/muxes/i2c-mux-pca9541.c        |  4 +---
 drivers/i2c/muxes/i2c-mux-pca954x.c        |  7 +------
 drivers/i2c/muxes/i2c-mux-pinctrl.c        |  4 +---
 drivers/i2c/muxes/i2c-mux-reg.c            |  4 +---
 drivers/iio/gyro/mpu3050-i2c.c             |  5 ++---
 drivers/media/usb/cx231xx/cx231xx-i2c.c    | 15 ++++-----------
 9 files changed, 18 insertions(+), 38 deletions(-)

-- 
2.1.4

Reply via email to