diff mbox

[stable] ov511: fix probe() hang due to double mutex_lock

Message ID 20091211204206.GB29049@jenkins.home.ifup.org (mailing list archive)
State Not Applicable
Headers show

Commit Message

Brandon Philips Dec. 11, 2009, 8:42 p.m. UTC
None
diff mbox

Patch

diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
index a452227..5d24504 100644
--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -36,6 +36,23 @@  Procedure for submitting patches to the -stable tree:
  - Security patches should not be sent to this alias, but instead to the
    documented security@kernel.org address.
 
+Submitting to -stable automatically upon reaching Linus's tree:
+
+ - As mentioned above, patches must be merged into Linus's tree before being
+   considered for -stable. But, if you are sending a patch for inclusion
+   into Linus's tree that you know you will eventually submit to -stable when
+   it is merged then you can save yourself the trouble of tracking the patch by
+   adding:
+
+     Cc: stable <stable@kernel.org>
+
+   in the signed-off-by area of the patch. Then once it is merged with Linus
+   an email with the patch will be sent to stable@kernel.org automatically.
+
+   This only works for patches that are for both -stable and Linus's tree at
+   the time of submission. If a fix has already made its way into Linus's tree
+   or a maintainer's queue for Linus's tree then follow the regular submission
+   rules outlined above.
 
 Review cycle: