From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Johannes Thumshirn <jth@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v6.1 2/2] btrfs: zoned: fix zone finishing with missing devices
Date: Fri, 18 Apr 2025 11:42:50 -0400 [thread overview]
Message-ID: <20250418090710-028f492dd52f129e@stable.kernel.org> (raw)
In-Reply-To: <6e7ceb08075b17b16898adc2b1add98c5ca58473.1744891500.git.jth@kernel.org>
[ 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: 35fec1089ebb5617f85884d3fa6a699ce6337a75
WARNING: Author mismatch between patch and upstream commit:
Backport author: Johannes Thumshirn<jth@kernel.org>
Commit author: Johannes Thumshirn<johannes.thumshirn@wdc.com>
Status in newer kernel trees:
6.14.y | Not found
6.13.y | Not found
6.12.y | Not found
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: 35fec1089ebb5 < -: ------------- btrfs: zoned: fix zone finishing with missing devices
-: ------------- > 1: a47a1104867b3 btrfs: zoned: fix zone finishing with missing devices
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-04-18 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 12:05 [PATCH v6.1 0/2] btrfs: stable backport for multidevice btrfs zone (de)activation Johannes Thumshirn
2025-04-17 12:05 ` [PATCH v6.1 1/2] btrfs: zoned: fix zone activation with missing devices Johannes Thumshirn
2025-04-18 15:42 ` Sasha Levin
2025-04-17 12:05 ` [PATCH v6.1 2/2] btrfs: zoned: fix zone finishing " Johannes Thumshirn
2025-04-18 15:42 ` 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=20250418090710-028f492dd52f129e@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox