All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, Zhi.Yang@eng.windriver.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] RDMA/core: Refactor rdma_bind_addr
Date: Mon, 12 May 2025 14:05:31 -0400	[thread overview]
Message-ID: <20250511192601-c785336a16cb65ea@stable.kernel.org> (raw)
In-Reply-To: <20250509024447.3959342-1-Zhi.Yang@eng.windriver.com>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
⚠️ Found follow-up fixes in mainline

The upstream commit SHA1 provided is correct: 8d037973d48c026224ab285e6a06985ccac6f7bf

WARNING: Author mismatch between patch and upstream commit:
Backport author: Zhi Yang<Zhi.Yang@eng.windriver.com>
Commit author: Patrisious Haddad<phaddad@nvidia.com>

Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (different SHA1: 88067197e97a)

Found fixes commits:
0e15863015d9 RDMA/core: Update CMA destination address on rdma_resolve_addr

Note: The patch differs from the upstream commit:
---
1:  8d037973d48c0 ! 1:  4144b6c866631 RDMA/core: Refactor rdma_bind_addr
    @@ Metadata
      ## Commit message ##
         RDMA/core: Refactor rdma_bind_addr
     
    +    commit 8d037973d48c026224ab285e6a06985ccac6f7bf upstream.
    +
         Refactor rdma_bind_addr function so that it doesn't require that the
         cma destination address be changed before calling it.
     
    @@ Commit message
         Reviewed-by: Mark Zhang <markzhang@nvidia.com>
         Link: https://lore.kernel.org/r/3d0e9a2fd62bc10ba02fed1c7c48a48638952320.1672819273.git.leonro@nvidia.com
         Signed-off-by: Leon Romanovsky <leon@kernel.org>
    +    Signed-off-by: Zhi Yang <Zhi.Yang@windriver.com>
    +    Signed-off-by: He Zhe <zhe.he@windriver.com>
     
      ## drivers/infiniband/core/cma.c ##
     @@ drivers/infiniband/core/cma.c: static int cma_resolve_ib_addr(struct rdma_id_private *id_priv)
---

Results of testing on various branches:

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

      reply	other threads:[~2025-05-12 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09  2:44 [PATCH 5.15.y] RDMA/core: Refactor rdma_bind_addr Zhi Yang
2025-05-12 18:05 ` 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=20250511192601-c785336a16cb65ea@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=Zhi.Yang@eng.windriver.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.