[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201201125445.GW2414@hirez.programming.kicks-ass.net>
Date: Tue, 1 Dec 2020 13:54:45 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
"Joel Fernandes (Google)" <joel@...lfernandes.org>,
Davidlohr Bueso <dbueso@...e.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 07/16] completion: drop init_completion define
On Tue, Dec 01, 2020 at 01:09:00PM +0100, Mauro Carvalho Chehab wrote:
> Changeset cd8084f91c02 ("locking/lockdep: Apply crossrelease to completions")
> added a CONFIG_LOCKDEP_COMPLETE (that was later renamed to
> CONFIG_LOCKDEP_COMPLETIONS).
>
> Such changeset renamed the init_completion, and add a macro
> that would either run a modified version or the original code.
>
> However, such code reported too many false positives. So, it
> ended being dropped later on by
> changeset e966eaeeb623 ("locking/lockdep: Remove the cross-release locking checks").
>
> Yet, the define remained there as just:
>
> #define init_completion(x) __init_completion(x)
>
> Get rid of the define, and return __init_completion() function
> to its original name.
>
> Fixes: e966eaeeb623 ("locking/lockdep: Remove the cross-release locking checks")
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> ---
Your patch is weird, did you add -C 1000 or something?
Powered by blists - more mailing lists