[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r0w9csqn.fsf@jogness.linutronix.de>
Date: Thu, 05 Jan 2023 09:10:16 +0106
From: John Ogness <john.ogness@...utronix.de>
To: "Paul E. McKenney" <paulmck@...nel.org>, rcu@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel-team@...a.com,
rostedt@...dmis.org, "Paul E. McKenney" <paulmck@...nel.org>,
Petr Mladek <pmladek@...e.com>
Subject: Re: [PATCH rcu 27/27] rcu: Remove CONFIG_SRCU
On 2023-01-04, "Paul E. McKenney" <paulmck@...nel.org> wrote:
> Now that all references to CONFIG_SRCU have been removed, it is time to
> remove CONFIG_SRCU itself.
I think "all references" is a bit misleading since there still are
several places in the kernel code that use it:
$ git grep CONFIG_SRCU
drivers/base/core.c:#ifdef CONFIG_SRCU
drivers/base/core.c:#else /* !CONFIG_SRCU */
drivers/base/core.c:#endif /* !CONFIG_SRCU */
fs/locks.c:#if IS_ENABLED(CONFIG_SRCU)
fs/locks.c:#else /* !IS_ENABLED(CONFIG_SRCU) */
fs/locks.c:#endif /* IS_ENABLED(CONFIG_SRCU) */
kernel/notifier.c:#ifdef CONFIG_SRCU
kernel/notifier.c:#endif /* CONFIG_SRCU */
Should those be removed before this patch?
John Ogness
Powered by blists - more mailing lists