From: "Paul E. McKenney" <paulmck@kernel.org>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Jens Axboe <axboe@kernel.dk>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, rostedt@goodmis.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH rcu 07/27] block: Remove "select SRCU"
Date: Thu, 5 Jan 2023 07:33:14 -0800 [thread overview]
Message-ID: <20230105153314.GS4028633@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <Y7aE2zzdTyjNId6w@osiris>
On Thu, Jan 05, 2023 at 09:05:47AM +0100, Heiko Carstens wrote:
> On Wed, Jan 04, 2023 at 05:43:07PM -0700, Jens Axboe wrote:
> > On 1/4/23 5:37 PM, 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.
> >
> > I'm assuming something earlier made this true (only CC'ed on this patch,
> > not the cover letter or interesting btis...), then:
>
> I was wondering the same. But it is already unconditionally enabled
> since commit 0cd7e350abc4 ("rcu: Make SRCU mandatory").
Ah, apologies for the terseness!
I took the coward's way out by making CONFIG_SRCU unconditional during
the last merge window and removing all references during this merge
window. ;-)
Thanx, Paul
next prev parent reply other threads:[~2023-01-05 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230105003759.GA1769545@paulmck-ThinkPad-P17-Gen-1>
2023-01-05 0:37 ` [PATCH rcu 07/27] block: Remove "select SRCU" Paul E. McKenney
2023-01-05 0:43 ` Jens Axboe
2023-01-05 8:05 ` Heiko Carstens
2023-01-05 15:33 ` Paul E. McKenney [this message]
2023-01-05 15:36 ` Jens Axboe
2023-01-05 15:48 ` 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=20230105153314.GS4028633@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=axboe@kernel.dk \
--cc=hca@linux.ibm.com \
--cc=kernel-team@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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