From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6 5/5] sched,freezer: Remove unnecessary warning in __thaw_task
Date: Mon, 28 Jul 2025 08:45:49 -0400 [thread overview]
Message-ID: <1753684648-09273728@stable.kernel.org> (raw)
In-Reply-To: <20250728025444.34009-6-chenridong@huaweicloud.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 9beb8c5e77dc10e3889ff5f967eeffba78617a88
WARNING: Author mismatch between patch and upstream commit:
Backport author: Chen Ridong <chenridong@huaweicloud.com>
Commit author: Chen Ridong <chenridong@huawei.com>
Status in newer kernel trees:
6.15.y | Not found
6.12.y | Not found
Note: Could not generate a diff with upstream commit:
---
Note: Could not generate diff - patch failed to apply for comparison
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 6.6 | Success | Success |
next prev parent reply other threads:[~2025-07-28 12:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250721125251.814862-1-sashal@kernel.org>
[not found] ` <1bafc8a024da4a95b28c02430f3d0c9d@huawei.com>
2025-07-22 1:29 ` Patch "Revert "cgroup_freezer: cgroup_freezing: Check if not frozen"" has been added to the 6.15-stable tree Chen Ridong
2025-07-22 12:18 ` Greg KH
2025-07-22 12:25 ` Chen Ridong
2025-07-22 12:38 ` Greg KH
2025-07-23 1:01 ` Chen Ridong
2025-07-23 5:06 ` Greg KH
2025-07-24 9:38 ` Chen Ridong
2025-07-24 9:43 ` Greg KH
2025-07-28 2:41 ` [PATCH 6.6 0/5] [Backport] sched,freezer: Remove unnecessary warning in __thaw_task Chen Ridong
2025-07-28 2:41 ` [PATCH 6.6 1/5] sched/core: Remove ifdeffery for saved_state Chen Ridong
2025-07-28 2:41 ` [PATCH 6.6 2/5] freezer,sched: Use saved_state to reduce some spurious wakeups Chen Ridong
2025-07-28 2:41 ` [PATCH 6.6 3/5] freezer,sched: Do not restore saved_state of a thawed task Chen Ridong
2025-07-28 2:41 ` [PATCH 6.6 4/5] freezer,sched: Clean saved_state when restoring it during thaw Chen Ridong
2025-07-28 2:41 ` [PATCH 6.6 5/5] sched,freezer: Remove unnecessary warning in __thaw_task Chen Ridong
2025-07-28 3:11 ` [PATCH 6.6 0/5] [Backport] " Chen Ridong
2025-07-28 2:54 ` Chen Ridong
2025-07-28 2:54 ` [PATCH 6.6 1/5] sched/core: Remove ifdeffery for saved_state Chen Ridong
2025-07-28 12:45 ` Sasha Levin
2025-07-28 2:54 ` [PATCH 6.6 2/5] freezer,sched: Use saved_state to reduce some spurious wakeups Chen Ridong
2025-07-28 12:45 ` Sasha Levin
2025-07-28 2:54 ` [PATCH 6.6 3/5] freezer,sched: Do not restore saved_state of a thawed task Chen Ridong
2025-07-28 12:49 ` Sasha Levin
2025-07-28 2:54 ` [PATCH 6.6 4/5] freezer,sched: Clean saved_state when restoring it during thaw Chen Ridong
2025-07-28 12:45 ` Sasha Levin
2025-07-28 2:54 ` [PATCH 6.6 5/5] sched,freezer: Remove unnecessary warning in __thaw_task Chen Ridong
2025-07-28 12:45 ` Sasha Levin [this message]
2025-07-29 13:22 ` Patch "Revert "cgroup_freezer: cgroup_freezing: Check if not frozen"" has been added to the 6.15-stable tree Chen Ridong
2025-07-29 14:33 ` Greg KH
2025-07-31 12:01 ` Chen Ridong
2025-07-31 12:13 ` Greg KH
2025-07-31 12:21 ` Chen Ridong
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=1753684648-09273728@stable.kernel.org \
--to=sashal@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 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.