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

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@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Will Deacon <will.deacon@arm.com>

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

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