All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] rdama: sync kernel headers and fix build
Date: Tue, 12 May 2026 14:45:08 +0300	[thread overview]
Message-ID: <20260512114508.GS15586@unreal> (raw)
In-Reply-To: <20260505181045.748088-1-stephen@networkplumber.org>

On Tue, May 05, 2026 at 11:10:44AM -0700, Stephen Hemminger wrote:
> The upstream kernel removed the 'RES_' prefix from RDMA netlink
> command and attribute names, but the rdma tool was still using
> the old names, causing build failures.
> 
> Update all references to match the new kernel header names:
> - RDMA_NLDEV_CMD_RES_FRMR_POOLS_* → RDMA_NLDEV_CMD_FRMR_POOLS_*
> - RDMA_NLDEV_ATTR_RES_FRMR_POOL* → RDMA_NLDEV_ATTR_FRMR_POOL*
> - RDMA_NLDEV_ATTR_FRMR_POOL_PINNED → RDMA_NLDEV_ATTR_FRMR_POOL_PINNED_HANDLES
> - RDMA_NLDEV_ATTR_FRMR_POOL_AGING_PERIOD → RDMA_NLDEV_ATTR_FRMR_POOLS_AGING_PERIOD
> 
>   Fixes build error:
>     res.h:203:26: error: 'RDMA_NLDEV_CMD_RES_FRMR_POOLS_GET' undeclared
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  rdma/include/uapi/rdma/rdma_netlink.h | 30 ++++----
>  rdma/res-frmr-pools.c                 | 98 +++++++++++++--------------
>  rdma/res.h                            |  2 +-
>  3 files changed, 65 insertions(+), 65 deletions(-)

There is a typo in the title: rdama -> rdma

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>

      reply	other threads:[~2026-05-12 11:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 18:10 [PATCH iproute2] rdama: sync kernel headers and fix build Stephen Hemminger
2026-05-12 11:45 ` Leon Romanovsky [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=20260512114508.GS15586@unreal \
    --to=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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.