public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
	Leon Romanovsky <leon@kernel.org>,
	linux-rdma@vger.kernel.org,
	Selvin Xavier <selvin.xavier@broadcom.com>,
	Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Cc: patches@lists.linux.dev
Subject: Re: [PATCH v3 00/13] Provide udata helpers and use them in bnxt_re
Date: Thu, 5 Mar 2026 20:47:49 -0400	[thread overview]
Message-ID: <20260306004749.GB2137346@nvidia.com> (raw)
In-Reply-To: <0-v3-bd56dd443069+49-bnxt_re_uapi_jgg@nvidia.com>

On Tue, Mar 03, 2026 at 03:49:57PM -0400, Jason Gunthorpe wrote:
> Jason Gunthorpe (13):
>   RDMA: Use copy_struct_from_user() instead of open coding
>   RDMA/core: Add rdma_udata_to_dev()
>   RDMA: Add ib_copy_validate_udata_in()
>   RDMA: Add ib_copy_validate_udata_in_cm()
>   RDMA: Add ib_respond_udata()
>   RDMA: Add ib_is_udata_in_empty()
>   RDMA: Provide documentation about the uABI compatibility rules
>   RDMA/bnxt_re: Add compatibility checks to the uapi path
>   RDMA/bnxt_re: Add compatibility checks to the uapi path for no data
>   RDMA/bnxt_re: Add missing comp_mask validation
>   RDMA/bnxt_re: Use ib_respond_udata()
>   RDMA/bnxt_re: Use ib_respond_empty_udata()
>   RDMA: Add IB_UVERBS_CORE_SUPPORT_ROBUST_UDATA

Applied to for-next

Jason

      parent reply	other threads:[~2026-03-06  0:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 19:49 [PATCH v3 00/13] Provide udata helpers and use them in bnxt_re Jason Gunthorpe
2026-03-03 19:49 ` [PATCH v3 01/13] RDMA: Use copy_struct_from_user() instead of open coding Jason Gunthorpe
2026-03-03 19:49 ` [PATCH v3 02/13] RDMA/core: Add rdma_udata_to_dev() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 03/13] RDMA: Add ib_copy_validate_udata_in() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 04/13] RDMA: Add ib_copy_validate_udata_in_cm() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 05/13] RDMA: Add ib_respond_udata() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 06/13] RDMA: Add ib_is_udata_in_empty() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 07/13] RDMA: Provide documentation about the uABI compatibility rules Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 08/13] RDMA/bnxt_re: Add compatibility checks to the uapi path Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 09/13] RDMA/bnxt_re: Add compatibility checks to the uapi path for no data Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 10/13] RDMA/bnxt_re: Add missing comp_mask validation Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 11/13] RDMA/bnxt_re: Use ib_respond_udata() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 12/13] RDMA/bnxt_re: Use ib_respond_empty_udata() Jason Gunthorpe
2026-03-03 19:50 ` [PATCH v3 13/13] RDMA: Add IB_UVERBS_CORE_SUPPORT_ROBUST_UDATA Jason Gunthorpe
2026-03-04  6:35   ` Sriharsha Basavapatna
2026-03-04 14:11     ` Jason Gunthorpe
2026-03-04 14:52       ` Sriharsha Basavapatna
2026-03-06  0:47 ` Jason Gunthorpe [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=20260306004749.GB2137346@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=selvin.xavier@broadcom.com \
    --cc=sriharsha.basavapatna@broadcom.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