From: Leon Romanovsky <leon@kernel.org>
To: jgg@ziepe.ca, Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Cc: linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com,
selvin.xavier@broadcom.com
Subject: Re: [PATCH rdma-next 0/3] bnxt_re driver update
Date: Sun, 06 Jul 2025 03:38:00 -0400 [thread overview]
Message-ID: <175178748069.897826.12893471590441976308.b4-ty@kernel.org> (raw)
In-Reply-To: <20250704043857.19158-1-kalesh-anakkur.purayil@broadcom.com>
On Fri, 04 Jul 2025 10:08:54 +0530, Kalesh AP wrote:
> This patchset adds support for 2G page size in the bnxt_re driver.
> There are couple of cosmetic changes as well.
>
> Kalesh AP (2):
> RDMA/bnxt_re: Fix size of uverbs_copy_to() in
> BNXT_RE_METHOD_GET_TOGGLE_MEM
> RDMA/bnxt_re: Use macro instead of hard coded value
>
> [...]
Applied, thanks!
[1/3] RDMA/bnxt_re: Fix size of uverbs_copy_to() in BNXT_RE_METHOD_GET_TOGGLE_MEM
https://git.kernel.org/rdma/rdma/c/8ba2e1eb6b3ec2
[2/3] RDMA/bnxt_re: Support 2G message size
https://git.kernel.org/rdma/rdma/c/c6acd006f110a0
[3/3] RDMA/bnxt_re: Use macro instead of hard coded value
https://git.kernel.org/rdma/rdma/c/bdc5726cdd454f
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2025-07-06 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 4:38 [PATCH rdma-next 0/3] bnxt_re driver update Kalesh AP
2025-07-04 4:38 ` [PATCH rdma-next 1/3] RDMA/bnxt_re: Fix size of uverbs_copy_to() in BNXT_RE_METHOD_GET_TOGGLE_MEM Kalesh AP
2025-07-04 4:38 ` [PATCH rdma-next 2/3] RDMA/bnxt_re: Support 2G message size Kalesh AP
2025-07-06 7:37 ` Leon Romanovsky
2025-07-07 2:34 ` Kalesh Anakkur Purayil
2025-07-04 4:38 ` [PATCH rdma-next 3/3] RDMA/bnxt_re: Use macro instead of hard coded value Kalesh AP
2025-07-06 7:38 ` Leon Romanovsky [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=175178748069.897826.12893471590441976308.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@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