From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, bvanassche@acm.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 1/3] block: remove rq_list_move
Date: Sat, 19 Apr 2025 07:47:04 -0400 [thread overview]
Message-ID: <20250418190043-a62bda61bc0991d7@stable.kernel.org> (raw)
In-Reply-To: <20250418175401.1936152-2-bvanassche@acm.org>
[ 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: e8225ab15006fbcdb14cef426a0a54475292fbbc
WARNING: Author mismatch between patch and found commit:
Backport author: Bart Van Assche<bvanassche@acm.org>
Commit author: Christoph Hellwig<hch@lst.de>
Note: The patch differs from the upstream commit:
---
1: e8225ab15006f < -: ------------- block: remove rq_list_move
-: ------------- > 1: 9bc5c94e278f7 Linux 6.14.2
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y | Success | Success |
next prev parent reply other threads:[~2025-04-19 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 17:53 [PATCH 0/3] Preserve the request order in the block layer Bart Van Assche
2025-04-18 17:53 ` [PATCH 1/3] block: remove rq_list_move Bart Van Assche
2025-04-19 11:47 ` Sasha Levin [this message]
2025-04-18 17:54 ` [PATCH 2/3] block: add a rq_list type Bart Van Assche
2025-04-19 11:47 ` Sasha Levin
2025-04-18 17:54 ` [PATCH 3/3] block: don't reorder requests in blk_add_rq_to_plug Bart Van Assche
2025-04-19 11:47 ` Sasha Levin
2025-04-22 11:51 ` [PATCH 0/3] Preserve the request order in the block layer Greg Kroah-Hartman
2025-05-04 17:14 ` Bart Van Assche
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=20250418190043-a62bda61bc0991d7@stable.kernel.org \
--to=sashal@kernel.org \
--cc=bvanassche@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox