This is a note to let you know that I've just added the patch titled
powerpc/tm: Update cause codes documentation
to the 3.9-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:
powerpc-tm-update-cause-codes-documentation.patch
and it can be found in the queue-3.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 24b92375dc4ec8a15262e8aaaab60b7404d4b1e7 Mon Sep 17 00:00:00 2001
From: Michael Neuling <mikey@xxxxxxxxxxx>
Date: Sun, 26 May 2013 18:09:38 +0000
Subject: powerpc/tm: Update cause codes documentation
From: Michael Neuling <mikey@xxxxxxxxxxx>
commit 24b92375dc4ec8a15262e8aaaab60b7404d4b1e7 upstream.
Signed-off-by: Michael Neuling <mikey@xxxxxxxxxxx>
Signed-off-by: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
Documentation/powerpc/transactional_memory.txt | 1 +
1 file changed, 1 insertion(+)
--- a/Documentation/powerpc/transactional_memory.txt
+++ b/Documentation/powerpc/transactional_memory.txt
@@ -155,6 +155,7 @@ These are defined in <asm/reg.h>, and di
kernel aborted a transaction:
TM_CAUSE_RESCHED Thread was rescheduled.
+ TM_CAUSE_TLBI Software TLB invalide.
TM_CAUSE_FAC_UNAV FP/VEC/VSX unavailable trap.
TM_CAUSE_SYSCALL Currently unused; future syscalls that must abort
transactions for consistency will use this.
Patches currently in stable-queue which might be from mikey@xxxxxxxxxxx are
queue-3.9/powerpc-tm-abort-on-emulation-and-alignment-faults.patch
queue-3.9/powerpc-tm-fix-userspace-stack-corruption-on-signal-delivery-for-active-transactions.patch
queue-3.9/powerpc-tm-update-cause-codes-documentation.patch
queue-3.9/powerpc-tm-make-room-for-hypervisor-in-abort-cause-codes.patch
queue-3.9/powerpc-tm-move-tm-abort-cause-codes-to-uapi.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