From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, benjamin@sipsolutions.net
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] um: work around sched_yield not yielding in time-travel mode
Date: Thu, 8 May 2025 21:52:42 -0400 [thread overview]
Message-ID: <20250508145118-02b51429410292e1@stable.kernel.org> (raw)
In-Reply-To: <20250314130815.226872-1-benjamin@sipsolutions.net>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: 887c5c12e80c8424bd471122d2e8b6b462e12874
WARNING: Author mismatch between patch and found commit:
Backport author: Benjamin Berg<benjamin@sipsolutions.net>
Commit author: Benjamin Berg<benjamin.berg@intel.com>
Note: The patch differs from the upstream commit:
---
1: 887c5c12e80c8 < -: ------------- um: work around sched_yield not yielding in time-travel mode
-: ------------- > 1: aeaee199900ee Linux 6.14.5
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y | Success | Success |
| stable/linux-6.12.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
| stable/linux-5.15.y | Success | Success |
| stable/linux-5.10.y | Success | Success |
| stable/linux-5.4.y | Success | Success |
prev parent reply other threads:[~2025-05-09 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 13:08 [PATCH] um: work around sched_yield not yielding in time-travel mode Benjamin Berg
2025-05-08 17:00 ` Missing patch in 6.12.27 - breaks UM target builds Christian Lamparter
2025-05-08 17:12 ` Benjamin Berg
2025-05-09 1:52 ` Sasha Levin [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=20250508145118-02b51429410292e1@stable.kernel.org \
--to=sashal@kernel.org \
--cc=benjamin@sipsolutions.net \
--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 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.