rt_patches: required rebase due to printk change

[hercules2020/nv-tegra/linux-4.4.git] / rt-patches / 0117-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch

diff --git a/rt-patches/0117-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch b/rt-patches/0117-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch
index ca8078e522e2eeafd3a91582df6421c5baf92b2c..6b9593ce87838cc7227f68044e5bb8ce199928b1 100644 (file)
--- a/rt-patches/0117-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch
+++ b/rt-patches/0117-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch
@@ -1,7 +1,7 @@
-From 5835bdc09769f3773aff8b75a827319123f66717 Mon Sep 17 00:00:00 2001
+From 9f95e3260a37233228392a4e1ec4c7738ae9c956 Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Fri, 1 Mar 2013 11:17:42 +0100
-Subject: [PATCH 117/365] futex: Ensure lock/unlock symetry versus pi_lock and
+Subject: [PATCH 117/366] futex: Ensure lock/unlock symetry versus pi_lock and
  hash bucket lock
 
 In exit_pi_state_list() we have the following locking construct:
@@ -45,5 +45,5 @@ index 33ddc99..1ec060b 100644
                }
  
 -- 
-2.7.4
+1.9.1