public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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.4/5.10] nvmet-fc: Remove unused functions
Date: Tue, 22 Apr 2025 15:46:05 -0400	[thread overview]
Message-ID: <20250422125255-a1c6fed2f6b4e83e@stable.kernel.org> (raw)
In-Reply-To: <E2B130726D65F768+20250422084611.103321-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
5.15.y | Not found
5.10.y | Not found

Note: The patch differs from the upstream commit:
---
1:  1b304c006b0fb ! 1:  e6a49ace3b0d5 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.
     
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y        |  Success    |  Success   |
| stable/linux-5.10.y       |  Success    |  Success   |

      reply	other threads:[~2025-04-22 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  8:46 [PATCH 5.4/5.10] nvmet-fc: Remove unused functions WangYuli
2025-04-22 19:46 ` 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=20250422125255-a1c6fed2f6b4e83e@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