rt_patches: required rebase due to printk change

[hercules2020/nv-tegra/linux-4.4.git] / rt-patches / 0113-rtmutex-trylock-is-okay-on-RT.patch

diff --git a/rt-patches/0113-rtmutex-trylock-is-okay-on-RT.patch b/rt-patches/0113-rtmutex-trylock-is-okay-on-RT.patch
index ff10d32f45beb9ae000453a4fdb4ebe78573d2bc..bf0eaf25e7db095d0e1aa56a07d564ee09b62541 100644 (file)
--- a/rt-patches/0113-rtmutex-trylock-is-okay-on-RT.patch
+++ b/rt-patches/0113-rtmutex-trylock-is-okay-on-RT.patch
@@ -1,7 +1,7 @@
-From de98879eab37675da7a36fce63f4b82ab5406ab0 Mon Sep 17 00:00:00 2001
+From a5dd12f982f6e5fbfd1b09356407bf078dd63f95 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Wed, 2 Dec 2015 11:34:07 +0100
-Subject: [PATCH 113/365] rtmutex: trylock is okay on -RT
+Subject: [PATCH 113/366] rtmutex: trylock is okay on -RT
 
 non-RT kernel could deadlock on rt_mutex_trylock() in softirq context. On
 -RT we don't run softirqs in IRQ context but in thread context so it is
@@ -29,5 +29,5 @@ index 397bd9e..01f4dc1 100644
  
        return rt_mutex_fasttrylock(lock, rt_mutex_slowtrylock);
 -- 
-2.7.4
+1.9.1