From: Greg KH <gregkh@linuxfoundation.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: stable@vger.kernel.org, "Paul E. McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Shuah Khan <shuah@kernel.org>,
rcu@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.15 1/2] torture: Avoid torture-test reboot loops
Date: Mon, 28 Aug 2023 11:56:40 +0200 [thread overview]
Message-ID: <2023082815-job-hull-9b54@gregkh> (raw)
In-Reply-To: <CAEXW_YTP9mm2f5YEL=Dbr399KomN6jd8Rwx+N1MXOuefs-vzoA@mail.gmail.com>
On Sun, Aug 27, 2023 at 06:31:55PM -0400, Joel Fernandes wrote:
> On Sun, Aug 27, 2023 at 6:27 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Sun, Aug 27, 2023 at 09:57:39PM +0000, Joel Fernandes (Google) wrote:
> > > From: "Paul E. McKenney" <paulmck@kernel.org>
> > >
> > > [ Upstream commit 10f84c2cfb5045e37d78cb5d4c8e8321e06ae18f ]
> >
> > I don't see this commit in Linus's tree, am I just missing it somewhere?
> >
>
> Ah, this particular patch might not be in Linus's tree yet. It is in
> Paul's tree. Feel free to ignore it for now if you want and I'll
> resend it later (and likewise for the 5.10 one).
Yeah, please just send it later, once it has landed in a -rc release
otherwise there's nothing we can do with it now, sorry.
thanks,
greg k-h
prev parent reply other threads:[~2023-08-28 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 21:57 [PATCH 5.15 1/2] torture: Avoid torture-test reboot loops Joel Fernandes (Google)
2023-08-27 21:57 ` [PATCH 5.15 2/2] rcu: Prevent expedited GP from enabling tick on offline CPU Joel Fernandes (Google)
2023-08-27 22:27 ` [PATCH 5.15 1/2] torture: Avoid torture-test reboot loops Greg KH
2023-08-27 22:31 ` Joel Fernandes
2023-08-28 9:56 ` Greg KH [this message]
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=2023082815-job-hull-9b54@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=stable@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 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).