From: Thomas Gleixner <tglx@kernel.org>
To: gregkh@linuxfoundation.org, dnaim@cachyos.org,
i.r.e.c.c.a.k.u.n+kernel.org@gmail.com
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] clockevents: Add missing resets of the next_event_forced flag" failed to apply to 7.0-stable tree
Date: Thu, 14 May 2026 12:50:32 +0200 [thread overview]
Message-ID: <87o6iiz2mf.ffs@tglx> (raw)
In-Reply-To: <2026051258-schedule-parcel-c95c@gregkh>
On Tue, May 12 2026 at 15:50, gregkh@linuxfoundation.org wrote:
> The patch below does not apply to the 7.0-stable tree.
Obviously not. It's in linux-7.0.y since April 22:
commit 9401b593fa48218d2667df1610b0ebc518554880
Author: Thomas Gleixner <tglx@kernel.org>
AuthorDate: Tue Apr 21 08:26:19 2026 +0200
Commit: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
CommitDate: Wed Apr 22 13:32:23 2026 +0200
clockevents: Add missing resets of the next_event_forced flag
commit 4096fd0e8eaea13ebe5206700b33f49635ae18e5 upstream.
next prev parent reply other threads:[~2026-05-14 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 13:50 FAILED: patch "[PATCH] clockevents: Add missing resets of the next_event_forced flag" failed to apply to 7.0-stable tree gregkh
2026-05-14 10:50 ` Thomas Gleixner [this message]
2026-05-14 12:52 ` Greg KH
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=87o6iiz2mf.ffs@tglx \
--to=tglx@kernel.org \
--cc=dnaim@cachyos.org \
--cc=gregkh@linuxfoundation.org \
--cc=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
--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