[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7ciswwMSdXhmsJbuf2jtrkUo=EXbYiWc2ZjA2PVPJz5rpw@mail.gmail.com>
Date: Tue, 8 Feb 2022 11:17:28 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Tejun Heo <tj@...nel.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>, Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>,
Boqun Feng <boqun.feng@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
Byungchul Park <byungchul.park@....com>,
"Paul E. McKenney" <paul.mckenney@...aro.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Radoslaw Burny <rburny@...gle.com>,
Lai Jiangshan <jiangshanlai@...il.com>
Subject: Re: [PATCH 04/12] workqueue: Protect lockdep functions with #ifdef
On Tue, Feb 8, 2022 at 10:48 AM Tejun Heo <tj@...nel.org> wrote:
>
> On Tue, Feb 08, 2022 at 10:42:00AM -0800, Namhyung Kim wrote:
> > With upcoming lock tracepoints config, it'd define some of lockdep
> > functions without enabling CONFIG_LOCKDEP actually. The existing code
> > assumes those functions will be removed by the preprocessor but it's
> > not the case anymore. Let's protect the code with #ifdef's explicitly.
> >
> > Cc: Tejun Heo <tj@...nel.org>
> > Cc: Lai Jiangshan <jiangshanlai@...il.com>
> > Signed-off-by: Namhyung Kim <namhyung@...nel.org>
>
> Can you wrap them in inlines and add some comment?
Ok, will do.
Thanks,
Namhyung
Powered by blists - more mailing lists