From: Mark Brown <broonie@kernel•org>
To: Jason Gunthorpe <jgg@nvidia•com>, Leon Romanovsky <leonro@nvidia•com>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Subject: Missing signoff in the rdma tree
Date: Mon, 9 Mar 2026 11:10:34 +0000 [thread overview]
Message-ID: <aa6qqi-GmXZXxubE@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
Commits
eb15cffa15201 ("RDMA/bnxt_re: Support application specific CQs")
485a21c14b413 ("RDMA/bnxt_re: Separate kernel and user CQ creation paths")
9ed273bbe6637 ("RDMA/bnxt_re: Refactor bnxt_re_create_cq()")
0edac801a2693 ("RDMA/bnxt_re: Support doorbell extensions")
4e99362444a2f ("RDMA/bnxt_re: Refactor bnxt_qplib_create_qp() function")
f0579e330b773 ("RDMA/bnxt_re: Move the UAPI methods to a dedicated file")
9db6a217ba5dd ("RDMA: Add IB_UVERBS_CORE_SUPPORT_ROBUST_UDATA")
ce150a8376e1e ("RDMA/bnxt_re: Use ib_respond_empty_udata()")
d59f007207b39 ("RDMA/bnxt_re: Use ib_respond_udata()")
ac4bb15208d1f ("RDMA/bnxt_re: Add missing comp_mask validation")
12c73bee53133 ("RDMA/bnxt_re: Add compatibility checks to the uapi path for no data")
ac593f5b66c9d ("RDMA/bnxt_re: Add compatibility checks to the uapi path")
6df3a6414d736 ("RDMA: Provide documentation about the uABI compatibility rules")
42d2a291ef474 ("RDMA: Add ib_is_udata_in_empty()")
f1cac281b4245 ("RDMA: Add ib_respond_udata()")
4ac738c6a7b90 ("RDMA: Add ib_copy_validate_udata_in_cm()")
715eccd4798ec ("RDMA: Add ib_copy_validate_udata_in()")
ea08d8cb8b520 ("RDMA/core: Add rdma_udata_to_dev()")
8e886928a19d7 ("RDMA: Use copy_struct_from_user() instead of open coding")
are missing a Signed-off-by from their committers
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-03-09 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 11:10 Mark Brown [this message]
2026-03-09 11:40 ` Missing signoff in the rdma tree Leon Romanovsky
2026-03-09 11:46 ` Mark Brown
2026-03-09 11:52 ` Leon Romanovsky
2026-03-09 12:43 ` Mark Brown
2026-03-09 12:48 ` Jason Gunthorpe
2026-04-06 16:38 ` Mark Brown
2026-04-06 17:30 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2026-03-23 13:25 Mark Brown
2026-03-30 22:10 ` Mark Brown
2026-03-31 4:59 ` Leon Romanovsky
2026-05-18 8:23 Mark Brown
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=aa6qqi-GmXZXxubE@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=jgg@nvidia$(echo .)com \
--cc=leonro@nvidia$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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