From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Gunthorpe <jgg@nvidia•com>, Leon Romanovsky <leonro@nvidia•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the rdma tree
Date: Thu, 11 Sep 2025 08:40:56 +1000 [thread overview]
Message-ID: <20250911084056.436a2c9f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
Hi all,
Commits
71c082d70547 ("RDMA/bnxt_re: Remove unnecessary condition checks")
d7fc2e1a321c ("RDMA/bnxt_re: Use firmware provided message timeout value")
d1dde88622b9 ("RDMA/bnxt_re: Initialize fw with roce_mirror support")
525b4368864c ("RDMA/bnxt_re: Add support for flow create/destroy")
c23c893e3a02 ("RDMA/bnxt_re: Add support for mirror vnic")
b8f4e7f1a275 ("RDMA/bnxt_re: Add support for unique GID")
bebe1a1bb1cf ("RDMA/bnxt_re: Refactor stats context memory allocation")
877d90abaa9e ("RDMA/bnxt_re: Refactor hw context memory allocation")
a99b2425cc60 ("RDMA/bnxt_re: Add data structures for RoCE mirror support")
47bd8cafcbf0 ("bnxt_en: Enhance stats context reservation logic")
are missing a Signed-off-by from their committers.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-09-10 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 22:40 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-26 8:26 linux-next: Signed-off-by missing for commit in the rdma tree Stephen Rothwell
2024-06-30 23:18 Stephen Rothwell
2022-10-27 19:33 Stephen Rothwell
2022-10-28 16:16 ` Jason Gunthorpe
2021-04-08 22:00 Stephen Rothwell
2021-04-09 16:20 ` Dennis Dalessandro
2021-04-09 16:46 ` Jason Gunthorpe
2018-11-08 22:13 Stephen Rothwell
2017-08-31 21:50 Stephen Rothwell
2017-09-01 12:06 ` Doug Ledford
2017-09-02 16:42 ` Linus Torvalds
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=20250911084056.436a2c9f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--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