From: Greg KH <greg@kroah.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: stable@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Steven Rostedt <rostedt@goodmis.org>,
Nicholas Piggin <npiggin@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 5.15 2/3] timers/nohz: Switch to ONESHOT_STOPPED in the low-res handler when the tick is stopped
Date: Sun, 13 Aug 2023 22:37:47 +0200 [thread overview]
Message-ID: <2023081327-capsule-drainer-38e4@gregkh> (raw)
In-Reply-To: <20230813202655.GB675119@google.com>
On Sun, Aug 13, 2023 at 08:26:55PM +0000, Joel Fernandes wrote:
> On Sun, Aug 13, 2023 at 03:16:19AM +0000, Joel Fernandes (Google) wrote:
> > From: Nicholas Piggin <npiggin@gmail.com>
> >
> > [ Upstream commit 5417ddc1cf1f5c8cba31ab217cf57ada7ab6ea88 ]
>
> I have the wrong SHA here, it should be: 62c1256d544747b38e77ca9b5bfe3a26f9592576
>
> If you don't mind correcting it, please go ahead. Or I can resend the patch
> in the future.
I've fixed this one up now, and queued up this series for 5.15.y now.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-13 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 3:16 [PATCH 5.15 1/3] tick: Detect and fix jiffies update stall Joel Fernandes (Google)
2023-08-13 3:16 ` [PATCH 5.15 2/3] timers/nohz: Switch to ONESHOT_STOPPED in the low-res handler when the tick is stopped Joel Fernandes (Google)
2023-08-13 20:26 ` Joel Fernandes
2023-08-13 20:37 ` Greg KH [this message]
2023-08-13 3:16 ` [PATCH 5.15 3/3] timers/nohz: Last resort update jiffies on nohz_full IRQ entry Joel Fernandes (Google)
-- strict thread matches above, loose matches on Subject: below --
2023-08-10 22:31 [PATCH 5.15 1/3] tick: Detect and fix jiffies update stall Joel Fernandes (Google)
2023-08-10 22:31 ` [PATCH 5.15 2/3] timers/nohz: Switch to ONESHOT_STOPPED in the low-res handler when the tick is stopped Joel Fernandes (Google)
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=2023081327-capsule-drainer-38e4@gregkh \
--to=greg@kroah.com \
--cc=joel@joelfernandes.org \
--cc=linux@roeck-us.net \
--cc=npiggin@gmail.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).