[lkml]   [2019]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH 0/1] lockdep: fix warning: print_lock_trace defined but not used
From: John Hubbard <>


This is a second attempt to send this. The first attempt [1]
went via, and did not receive a DKIM signature,
so I think it probably got discarded by many systems.

This one goes via gmail, which is what I was using before. We'll keep
working on getting the NVIDIA outgoing email servers working
with mailing lists, but meanwhile I'm back to using "envelope"
techniques, I guess. I was hoping to use a "native" email
address, but not quite there yet. :)

Anyway, here's the original cover letter:

I ran across this minor warning while building against today's linux.git.

The proposed trivial fix leaves it a little fragile from a "what if someone
adds a new call to print_lock_trace()" point of view, but I believe that it
makes the current combination of ifdefs accurate, anyway.


Cc: Frederic Weisbecker <>
Cc: Andrew Morton <>
Cc: Linus Torvalds <>
Cc: Paul E. McKenney <>
Cc: Peter Zijlstra <>
Cc: Thomas Gleixner <>
Cc: Will Deacon <>

John Hubbard (1):
lockdep: fix warning: print_lock_trace defined but not used

kernel/locking/lockdep.c | 3 +++
1 file changed, 3 insertions(+)


 \ /
  Last update: 2019-05-21 09:09    [W:0.085 / U:4.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site