From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, songmuchun@bytedance.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] block: fix missing dispatching request when queue is started or unquiesced
Date: Mon, 17 Mar 2025 12:40:10 -0400 [thread overview]
Message-ID: <20250317093129-b12d4b529eda4b6a@stable.kernel.org> (raw)
In-Reply-To: <20250317071821.22449-1-songmuchun@bytedance.com>
[ 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: 2003ee8a9aa14d766b06088156978d53c2e9be3d
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 8b25c0a165dd)
6.6.y | Present (different SHA1: fe0d9800ead6)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 2003ee8a9aa14 < -: ------------- block: fix missing dispatching request when queue is started or unquiesced
-: ------------- > 1: 78009b03feb87 block: fix missing dispatching request when queue is started or unquiesced
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-03-17 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 10:10 FAILED: patch "[PATCH] block: fix missing dispatching request when queue is started" failed to apply to 5.15-stable tree gregkh
2025-03-17 3:30 ` [PATCH 5.15.y] block: fix missing dispatching request when queue is started or unquiesced Muchun Song
2025-03-17 6:56 ` Greg KH
2025-03-17 16:39 ` Sasha Levin
2025-03-17 7:18 ` Muchun Song
2025-03-17 16:40 ` Sasha Levin [this message]
2025-04-22 12:20 ` 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=20250317093129-b12d4b529eda4b6a@stable.kernel.org \
--to=sashal@kernel.org \
--cc=songmuchun@bytedance.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