This is a note to let you know that I've just added the patch titled
mtd: devices: elm: fix elm_context_save() and elm_context_restore() functions
to the 3.14-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:
mtd-devices-elm-fix-elm_context_save-and-elm_context_restore-functions.patch
and it can be found in the queue-3.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 6938ad40cb97a52d88a763008935340729a4acc7 Mon Sep 17 00:00:00 2001
From: Ted Juan <ted.juan@xxxxxxxxx>
Date: Fri, 20 Jun 2014 17:32:05 +0800
Subject: mtd: devices: elm: fix elm_context_save() and elm_context_restore() functions
From: Ted Juan <ted.juan@xxxxxxxxx>
commit 6938ad40cb97a52d88a763008935340729a4acc7 upstream.
These two function's switch case lack the 'break' that make them always
return error.
Signed-off-by: Ted Juan <ted.juan@xxxxxxxxx>
Acked-by: Pekon Gupta <pekon@xxxxxx>
Signed-off-by: Brian Norris <computersforpeace@xxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/mtd/devices/elm.c | 2 ++
1 file changed, 2 insertions(+)
--- a/drivers/mtd/devices/elm.c
+++ b/drivers/mtd/devices/elm.c
@@ -428,6 +428,7 @@ static int elm_context_save(struct elm_i
ELM_SYNDROME_FRAGMENT_1 + offset);
regs->elm_syndrome_fragment_0[i] = elm_read_reg(info,
ELM_SYNDROME_FRAGMENT_0 + offset);
+ break;
default:
return -EINVAL;
}
@@ -466,6 +467,7 @@ static int elm_context_restore(struct el
regs->elm_syndrome_fragment_1[i]);
elm_write_reg(info, ELM_SYNDROME_FRAGMENT_0 + offset,
regs->elm_syndrome_fragment_0[i]);
+ break;
default:
return -EINVAL;
}
Patches currently in stable-queue which might be from ted.juan@xxxxxxxxx are
queue-3.14/mtd-devices-elm-fix-elm_context_save-and-elm_context_restore-functions.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