From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: WangYuli <wangyuli@uniontech.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15/6.1/6.6] nvmet-fc: Remove unused functions
Date: Tue, 22 Apr 2025 15:45:54 -0400 [thread overview]
Message-ID: <20250422114901-d91b46a9b40ebe2f@stable.kernel.org> (raw)
In-Reply-To: <85E64841B89AA153+20250422084047.100708-1-wangyuli@uniontech.com>
[ 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: 1b304c006b0fb4f0517a8c4ba8c46e88f48a069c
Status in newer kernel trees:
6.14.y | Not found
6.12.y | Not found
6.6.y | Not found
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 1b304c006b0fb ! 1: b1866793ad4fe nvmet-fc: Remove unused functions
@@ Metadata
## Commit message ##
nvmet-fc: Remove unused functions
+ [ Upstream commit 1b304c006b0fb4f0517a8c4ba8c46e88f48a069c ]
+
The functions nvmet_fc_iodnum() and nvmet_fc_fodnum() are currently
unutilized.
@@ Commit message
## drivers/nvme/target/fc.c ##
@@ drivers/nvme/target/fc.c: struct nvmet_fc_tgt_assoc {
- struct work_struct del_work;
+ struct rcu_head rcu;
};
-
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-04-22 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 8:40 [PATCH 5.15/6.1/6.6] nvmet-fc: Remove unused functions WangYuli
2025-04-22 19:45 ` 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=20250422114901-d91b46a9b40ebe2f@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wangyuli@uniontech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox