https://patchwork.kernel.org/patch/9249063

(Oh I see you're uploading now.)

Waiting for feedback from maintainer

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/71e479eb4a35b7745abcb0a43cee70e3970eff71

commit 71e479eb4a35b7745abcb0a43cee70e3970eff71
Author: Guenter Roeck <linux@roeck-us.net>
Date: Tue Jul 26 22:34:01 2016

FROMLIST: i2c: i2c-cros-ec-tunnel: Reduce logging noise

If an i2c access through i2c-cros-ec-tunnel returns an error, the following
log message is seen on the console.

cros-ec-i2c-tunnel ff200000.spi:ec@0:i2c-tunnel:
			Error parsing EC i2c message -121

This can happen a lot if, for example, the i2c-detect command is executed.

Since it is perfectly normal for an i2c controller to report an error,
drop the message. Also, report -ENXIO instead of -EREMOTEIO if the access
error is due to NAK from the device, and return -EIO instead of -EREMOTEIO
for other errors, as suggested in Documentation/i2c/fault-codes.

BUG= chromium:631172 , chrome-os-partner:55954
TEST=Boot any system with i2c-cros-ec-tunnel and run i2cdetect

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/9249063/mbox/)
Signed-off-by: Guenter Roeck <groeck@chromium.org>

Change-Id: Ic456d523ca0da6c559cb148828001cd958b1a993
Reviewed-on: https://chromium-review.googlesource.com/376957
Reviewed-by: Katie Roberts-Hoffman <katierh@chromium.org>
Commit-Queue: Wonjoon Lee <woojoo.lee@samsung.com>
Tested-by: Wonjoon Lee <woojoo.lee@samsung.com>

[modify] https://crrev.com/71e479eb4a35b7745abcb0a43cee70e3970eff71/drivers/i2c/busses/i2c-cros-ec-tunnel.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/f2f7c3b0dc189d2427b81e91e2fe31d53d079e2f

commit f2f7c3b0dc189d2427b81e91e2fe31d53d079e2f
Author: Guenter Roeck <linux@roeck-us.net>
Date: Tue Jul 26 22:34:01 2016

FROMLIST: i2c: i2c-cros-ec-tunnel: Reduce logging noise

If an i2c access through i2c-cros-ec-tunnel returns an error, the following
log message is seen on the console.

cros-ec-i2c-tunnel ff200000.spi:ec@0:i2c-tunnel:
			Error parsing EC i2c message -121

This can happen a lot if, for example, the i2c-detect command is executed.

Since it is perfectly normal for an i2c controller to report an error,
drop the message. Also, report -ENXIO instead of -EREMOTEIO if the access
error is due to NAK from the device, and return -EIO instead of -EREMOTEIO
for other errors, as suggested in Documentation/i2c/fault-codes.

BUG= chromium:631172 , chrome-os-partner:55954
TEST=Boot any system with i2c-cros-ec-tunnel and run i2cdetect

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/9249063/mbox/)
Signed-off-by: Guenter Roeck <groeck@chromium.org>

Change-Id: Ic456d523ca0da6c559cb148828001cd958b1a993
Reviewed-on: https://chromium-review.googlesource.com/366560
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Guenter Roeck <groeck@chromium.org>
Tested-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/f2f7c3b0dc189d2427b81e91e2fe31d53d079e2f/drivers/i2c/busses/i2c-cros-ec-tunnel.c

Calling this one fixed. Please feel free to reopen if needed.

Also, w.r.t. Chromium, this is "Chrome" OS, not "Linux" :)