From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joel@joelfernandes.org>,
stable-commits@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>
Subject: Re: Patch "rcu: Make call_rcu() lazy to save power" has been added to the 6.1-stable tree
Date: Mon, 23 Oct 2023 15:08:44 +0200 [thread overview]
Message-ID: <2023102303-pending-purity-c504@gregkh> (raw)
In-Reply-To: <ZTZt0FrBteUJpxf_@sashalap>
On Mon, Oct 23, 2023 at 08:57:52AM -0400, Sasha Levin wrote:
> On Sat, Oct 21, 2023 at 12:23:33PM -0400, Joel Fernandes wrote:
> > On Fri, Oct 20, 2023 at 8:18 PM Sasha Levin <sashal@kernel.org> wrote:
> > >
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > rcu: Make call_rcu() lazy to save power
> > >
> > > to the 6.1-stable tree which can be found at:
> > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > Sasha, could you drop this patch from 6.1 stable? It is a new feature
> > and as such I expect folks who need it to backport. For instance, in
> > our stable derivatives, it has been backported.
>
> You're right that it's a new feature, but it was taken as a dependency
> for a later fix.
I resolved this, and removed it, it wasn't really needed for that fix,
your bot's dependency chain got a bit too long for a 2 line bugfix :)
thanks,
greg k-h
parent reply other threads:[~2023-10-23 13:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ZTZt0FrBteUJpxf_@sashalap>]
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=2023102303-pending-purity-c504@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=quic_neeraju@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=stable-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.