From: Jan Kara <jack@suse.cz>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, rostedt@goodmis.org,
Jan Kara <jack@suse.cz>, Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH rcu 20/27] fs/notify: Remove "select SRCU"
Date: Thu, 5 Jan 2023 12:30:05 +0100 [thread overview]
Message-ID: <20230105113005.qmwz4bcxffy265ps@quack3> (raw)
In-Reply-To: <20230105003813.1770367-20-paulmck@kernel.org>
On Wed 04-01-23 16:38:06, Paul E. McKenney wrote:
> Now that the SRCU Kconfig option is unconditionally selected, there is
> no longer any point in selecting it. Therefore, remove the "select SRCU"
> Kconfig statements.
>
> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> Cc: Jan Kara <jack@suse.cz>
> Cc: Amir Goldstein <amir73il@gmail.com>
> Cc: <linux-fsdevel@vger.kernel.org>
Sure. You can add:
Acked-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/notify/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/fs/notify/Kconfig b/fs/notify/Kconfig
> index c020d26ba223e..c6c72c90fd253 100644
> --- a/fs/notify/Kconfig
> +++ b/fs/notify/Kconfig
> @@ -1,7 +1,6 @@
> # SPDX-License-Identifier: GPL-2.0-only
> config FSNOTIFY
> def_bool n
> - select SRCU
>
> source "fs/notify/dnotify/Kconfig"
> source "fs/notify/inotify/Kconfig"
> --
> 2.31.1.189.g2e36527f23
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-01-05 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230105003759.GA1769545@paulmck-ThinkPad-P17-Gen-1>
2023-01-05 0:38 ` [PATCH rcu 20/27] fs/notify: Remove "select SRCU" Paul E. McKenney
2023-01-05 11:30 ` Jan Kara [this message]
2023-01-05 0:38 ` [PATCH rcu 25/27] fs: Remove CONFIG_SRCU Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230105113005.qmwz4bcxffy265ps@quack3 \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).