[PATCH 0/1] lockdep: fix warning: print_lock_trace defined but not used
From: john . hubbard
Date: Tue May 21 2019 - 03:10:44 EST
From: John Hubbard <jhubbard@xxxxxxxxxx>
Hi,
This is a second attempt to send this. The first attempt [1]
went via mailgw.nvidia.com, 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.
[1] https://lkml.org/lkml/2019/5/19/60
Cc: Frederic Weisbecker <frederic@xxxxxxxxxx>
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Cc: Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx>
Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Cc: Will Deacon <will.deacon@xxxxxxx>
John Hubbard (1):
lockdep: fix warning: print_lock_trace defined but not used
kernel/locking/lockdep.c | 3 +++
1 file changed, 3 insertions(+)
--
2.21.0