The patch titled
gpio: sx150x: fix error code value
has been added to the -mm tree. Its filename is
gpio-sx150x-fix-error-code-value.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: gpio: sx150x: fix error code value
From: Vasiliy Kulikov <segooon@xxxxxxxxx>
The return code of sx150x_get_io() is propagated as error code, so it
should look like standard code.
Signed-off-by: Vasiliy Kulikov <segooon@xxxxxxxxx>
Cc: Gregory Bean <gbean@xxxxxxxxxxxxxx>
Cc: Jean Delvare <khali@xxxxxxxxxxxx>
Cc: David Brownell <david-b@xxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/gpio/sx150x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/gpio/sx150x.c~gpio-sx150x-fix-error-code-value drivers/gpio/sx150x.c
--- a/drivers/gpio/sx150x.c~gpio-sx150x-fix-error-code-value
+++ a/drivers/gpio/sx150x.c
@@ -179,7 +179,7 @@ static int sx150x_get_io(struct sx150x_c
sx150x_find_cfg(offset, 1, ®, &mask, &shift);
err = sx150x_i2c_read(chip->client, reg, &data);
if (err >= 0)
- err = (data & mask) != 0 ? 1 : 0;
+ err = (data & mask) != 0 ? -EIO : 0;
return err;
}
_
Patches currently in -mm which might be from segooon@xxxxxxxxx are
linux-next.patch
md-check-return-code-of-read_sb_page.patch
mm-mempolicy-check-return-code-of-check_range.patch
drivers-rtc-classc-fix-device_register-error-handling.patch
gpio-sx150x-fix-error-code-value.patch
memstick-core-fix-device_register-error-handling.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
