This is a note to let you know that I've just added the patch titled
mmc: slot-gpio: Fix missing assignment to ctx->ro_gpio
to the 3.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
mmc-slot-gpio-fix-missing-assignment-to-ctx-ro_gpio.patch
and it can be found in the queue-3.6 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 15e8a8e42966162c207bb97ed55c803bc437eeae Mon Sep 17 00:00:00 2001
From: Chris Ball <[email protected]>
Date: Sun, 9 Sep 2012 22:56:48 -0400
Subject: mmc: slot-gpio: Fix missing assignment to ctx->ro_gpio
From: Chris Ball <[email protected]>
commit 15e8a8e42966162c207bb97ed55c803bc437eeae upstream.
mmc_gpio_request_ro() doesn't store the requested gpio in ctx->ro_gpio.
As a result, subsequent calls to mmc_gpio_get_ro() will always fail
with -ENOSYS because the gpio number isn't available to that function.
Acked-by: Guennadi Liakhovetski <[email protected]>
Signed-off-by: Chris Ball <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/mmc/core/slot-gpio.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--- a/drivers/mmc/core/slot-gpio.c
+++ b/drivers/mmc/core/slot-gpio.c
@@ -100,7 +100,13 @@ int mmc_gpio_request_ro(struct mmc_host
ctx = host->slot.handler_priv;
- return gpio_request_one(gpio, GPIOF_DIR_IN, ctx->ro_label);
+ ret = gpio_request_one(gpio, GPIOF_DIR_IN, ctx->ro_label);
+ if (ret < 0)
+ return ret;
+
+ ctx->ro_gpio = gpio;
+
+ return 0;
}
EXPORT_SYMBOL(mmc_gpio_request_ro);
Patches currently in stable-queue which might be from [email protected] are
queue-3.6/mmc-slot-gpio-fix-missing-assignment-to-ctx-ro_gpio.patch
queue-3.6/mmc-sh-mmcif-avoid-oops-on-spurious-interrupts.patch
queue-3.6/mmc-omap_hsmmc-pass-on-the-suspend-failure-to-the-pm-core.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
