Netdev List
 help / color / mirror / Atom feed
From: Chiara Meiohas <cmeiohas@nvidia.com>
To: David Ahern <dsahern@gmail.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: leon@kernel.org, michaelgur@nvidia.com, jgg@nvidia.com,
	linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
	Patrisious Haddad <phaddad@nvidia.com>
Subject: Re: [PATCH v2 iproute2-next 1/4] rdma: Update headers
Date: Thu, 7 May 2026 22:03:04 +0300	[thread overview]
Message-ID: <7f4f54c0-a71f-4664-b934-9ae71e8c5056@nvidia.com> (raw)
In-Reply-To: <3cf0dcca-9a3f-4cee-83d7-f058f33bcc04@gmail.com>

On 07/05/2026 19:20, David Ahern wrote:

> On 4/28/26 4:05 AM, Chiara Meiohas wrote:
>> We will prepare a sync patch to align the names with the kernel and send
>> it shortly.
> what happened to this request? I see that Stephen had to post a patch
> (not yet applied) to address this problem:
>
> https://patchwork.kernel.org/project/netdevbpf/patch/20260505181045.748088-1-stephen@networkplumber.org/
>
> We allow rdma to have separate uapi headers for convenience. Responses
> to mistakes need to be timely.

Hi David,

My apologies for the delay; I will make sure these mistakes are handled

more promptly in the future.


I have sent our version to the mailing list, as I was not sure how you

would prefer to proceed given the overlap.

https://lore.kernel.org/linux-rdma/20260507184609.3439875-1-cmeiohas@nvidia.com/

Thanks,

Chiara


  reply	other threads:[~2026-05-07 19:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 17:31 [PATCH v2 iproute2-next 0/4] Introduce FRMR pools Chiara Meiohas
2026-03-30 17:31 ` [PATCH v2 iproute2-next 1/4] rdma: Update headers Chiara Meiohas
2026-04-27 18:25   ` Stephen Hemminger
2026-04-27 18:27     ` David Ahern
2026-04-28 10:05       ` Chiara Meiohas
2026-05-07 16:20         ` David Ahern
2026-05-07 19:03           ` Chiara Meiohas [this message]
2026-03-30 17:31 ` [PATCH v2 iproute2-next 2/4] rdma: Add resource FRMR pools show command Chiara Meiohas
2026-03-30 17:31 ` [PATCH v2 iproute2-next 3/4] rdma: Add FRMR pools set aging command Chiara Meiohas
2026-03-30 17:31 ` [PATCH v2 iproute2-next 4/4] rdma: Add FRMR pools set pinned command Chiara Meiohas
2026-04-05 17:09 ` [PATCH v2 iproute2-next 0/4] Introduce FRMR pools David Ahern
2026-04-05 17:44   ` Chiara Meiohas
2026-04-27 18:20   ` Stephen Hemminger
2026-04-27 18:22     ` Jason Gunthorpe
2026-04-05 17:10 ` patchwork-bot+netdevbpf

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=7f4f54c0-a71f-4664-b934-9ae71e8c5056@nvidia.com \
    --to=cmeiohas@nvidia.com \
    --cc=dsahern@gmail.com \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michaelgur@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=phaddad@nvidia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox