[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190521070808.3536-1-jhubbard@nvidia.com>
Date: Tue, 21 May 2019 00:08:07 -0700
From: john.hubbard@...il.com
To: LKML <linux-kernel@...r.kernel.org>
Cc: John Hubbard <jhubbard@...dia.com>,
Frederic Weisbecker <frederic@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Will Deacon <will.deacon@....com>
Subject: [PATCH 0/1] lockdep: fix warning: print_lock_trace defined but not used
From: John Hubbard <jhubbard@...dia.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@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: Will Deacon <will.deacon@....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
Powered by blists - more mailing lists