From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Yu Kuai <yukuai1@huaweicloud.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12 5/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer
Date: Mon, 27 Jan 2025 06:25:15 -0500 [thread overview]
Message-ID: <20250127042655-23e1158f105baa74@stable.kernel.org> (raw)
In-Reply-To: <20250127085214.3197761-6-yukuai1@huaweicloud.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: cd5fc653381811f1e0ba65f5d169918cab61476f
WARNING: Author mismatch between patch and upstream commit:
Backport author: Yu Kuai<yukuai1@huaweicloud.com>
Commit author: Yu Kuai<yukuai3@huawei.com>
Status in newer kernel trees:
6.12.y | Not found
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
prev parent reply other threads:[~2025-01-27 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 8:52 [PATCH 6.12 0/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-01-27 8:52 ` [PATCH 6.12 1/5] md/md-bitmap: factor behind write counters out from bitmap_{start/end}write() Yu Kuai
2025-01-27 11:25 ` Sasha Levin
2025-01-27 8:52 ` [PATCH 6.12 2/5] md/md-bitmap: remove the last parameter for bimtap_ops->endwrite() Yu Kuai
2025-01-27 11:25 ` Sasha Levin
2025-01-27 8:52 ` [PATCH 6.12 3/5] md: add a new callback pers->bitmap_sector() Yu Kuai
2025-01-27 11:25 ` Sasha Levin
2025-01-27 8:52 ` [PATCH 6.12 4/5] md/raid5: implement pers->bitmap_sector() Yu Kuai
2025-01-27 11:25 ` Sasha Levin
2025-01-27 8:52 ` [PATCH 6.12 5/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-01-27 11:25 ` 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=20250127042655-23e1158f105baa74@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yukuai1@huaweicloud.com \
/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.