This is a note to let you know that I've just added the patch titled
i2c: rk3x: populate correct variable for sda_falling_time
to the 4.3-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:
i2c-rk3x-populate-correct-variable-for-sda_falling_time.patch
and it can be found in the queue-4.3 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 9abd29e7c13de24ce73213a425d9574b35ac0c6a Mon Sep 17 00:00:00 2001
From: Wolfram Sang <wsa@xxxxxxxxxxxxx>
Date: Wed, 25 Nov 2015 16:58:18 +0100
Subject: i2c: rk3x: populate correct variable for sda_falling_time
From: Wolfram Sang <wsa@xxxxxxxxxxxxx>
commit 9abd29e7c13de24ce73213a425d9574b35ac0c6a upstream.
Signed-off-by: Wolfram Sang <wsa@xxxxxxxxxxxxx>
Reviewed-by: Douglas Anderson <dianders@xxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/i2c/busses/i2c-rk3x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/i2c/busses/i2c-rk3x.c
+++ b/drivers/i2c/busses/i2c-rk3x.c
@@ -907,7 +907,7 @@ static int rk3x_i2c_probe(struct platfor
&i2c->scl_fall_ns))
i2c->scl_fall_ns = 300;
if (of_property_read_u32(pdev->dev.of_node, "i2c-sda-falling-time-ns",
- &i2c->scl_fall_ns))
+ &i2c->sda_fall_ns))
i2c->sda_fall_ns = i2c->scl_fall_ns;
strlcpy(i2c->adap.name, "rk3x-i2c", sizeof(i2c->adap.name));
Patches currently in stable-queue which might be from wsa@xxxxxxxxxxxxx are
queue-4.3/i2c-rcar-disable-runtime-pm-correctly-in-slave-mode.patch
queue-4.3/i2c-fix-wakeup-irq-parsing.patch
queue-4.3/i2c-rk3x-populate-correct-variable-for-sda_falling_time.patch
queue-4.3/i2c-mv64xxx-the-n-clockdiv-factor-is-0-based-on-sunxi-socs.patch
queue-4.3/i2c-at91-fix-write-transfers-by-clearing-pending-interrupt-first.patch
queue-4.3/i2c-at91-manage-unexpected-rxrdy-flag-when-starting-a-transfer.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html