Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "David Hu" <dhu@x6u.co>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next v4 4/6] RDMA/irdma: Split CQ setup to umode and kmode
Date: Fri, 30 Oct 2026 18:30:55 +0000	[thread overview]
Message-ID: <sashiko-outbox-191410@kernel.org> (raw)
In-Reply-To: <20261030181512.2056056-5-dhu@x6u.co>

> From: David Hu <xuehaohu@google.com>
> 
> Add user mode cq callback `irdma_create_user_cq()` to separate out user
> mode creation logic from kernel mode cq.
> 
> Original common setup logic is broken into shared helper routines, so
> duplicate code can be avoided. Core creation logic is preserved to be
> identical to original routine, however.
> 
> Signed-off-by: David Hu <xuehaohu@google.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261030181512.2056056-1-dhu@x6u.co?part=4


  reply	other threads:[~2026-10-30 18:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 18:15 [PATCH rdma-next v4 0/6] RDMA/irdma: Add support for ioctl David Hu
2026-10-30 18:15 ` [PATCH rdma-next v4 1/6] RDMA/irdma: Plumb uverbs_attr_bundle for QP, SRQ David Hu
2026-10-30 18:23   ` sashiko-bot
2026-10-30 18:15 ` [PATCH rdma-next v4 2/6] RDMA/irdma: Register irdma UVERBS ioctl namespace David Hu
2026-10-30 18:23   ` sashiko-bot
2026-10-30 18:15 ` [PATCH rdma-next v4 3/6] RDMA/irdma: Support UMEM attribute for QP creation David Hu
2026-10-30 18:26   ` sashiko-bot
2026-10-30 18:15 ` [PATCH rdma-next v4 4/6] RDMA/irdma: Split CQ setup to umode and kmode David Hu
2026-10-30 18:30   ` sashiko-bot [this message]
2026-10-30 18:15 ` [PATCH rdma-next v4 5/6] RDMA/irdma: Support UMEM attribute for CQ creation David Hu
2026-10-30 18:33   ` sashiko-bot
2026-10-30 18:15 ` [PATCH rdma-next v4 6/6] RDMA/irdma: Support UMEM attribute for SRQ creation David Hu
2026-10-30 18:34   ` sashiko-bot

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=sashiko-outbox-191410@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dhu@x6u.co \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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