From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Hagar Hemdan <hagarhem@amazon.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1] nvme: fix metadata handling in nvme-passthrough
Date: Mon, 3 Feb 2025 07:37:40 -0500 [thread overview]
Message-ID: <20250203063017-289a829a3da5601a@stable.kernel.org> (raw)
In-Reply-To: <20250203082501.28771-1-hagarhem@amazon.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 7c2fd76048e95dd267055b5f5e0a48e6e7c81fd9
WARNING: Author mismatch between patch and upstream commit:
Backport author: Hagar Hemdan<hagarhem@amazon.com>
Commit author: Puranjay Mohan<pjy@amazon.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 6b42ded89ba8)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 7c2fd76048e95 < -: ------------- nvme: fix metadata handling in nvme-passthrough
-: ------------- > 1: 93de7cb0266e2 nvme: fix metadata handling in nvme-passthrough
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-02-03 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 8:24 [PATCH 6.1] nvme: fix metadata handling in nvme-passthrough Hagar Hemdan
2025-02-03 12:37 ` Sasha Levin [this message]
2025-02-04 13:56 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2024-11-25 12:10 [PATCH 6.6] " Hagar Hemdan
2024-11-25 12:10 ` [PATCH 6.1] " Hagar Hemdan
2024-11-25 15:20 ` Sasha Levin
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=20250203063017-289a829a3da5601a@stable.kernel.org \
--to=sashal@kernel.org \
--cc=hagarhem@amazon.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 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.