From: Selvin Xavier <selvin.xavier@broadcom.com>
To: leon@kernel.org, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com,
kalesh-anakkur.purayil@broadcom.com,
Selvin Xavier <selvin.xavier@broadcom.com>
Subject: [PATCH for-next 0/2] RDMA/bnxt_re: Driver update
Date: Thu, 9 Jan 2025 10:18:11 -0800 [thread overview]
Message-ID: <1736446693-6692-1-git-send-email-selvin.xavier@broadcom.com> (raw)
Generic updates to bnxt_re driver. Pass the info that indicates
the context of the caller in ulp_irq_stop. Also, code reorganization
to optimize the device data structure.
This series is created on top of the changes from Kalesh
https://patchwork.kernel.org/project/linux-rdma/list/?series=922731
Please review and apply.
Thanks,
Selvin Xavier
Kalesh AP (2):
RDMA/bnxt_re: Pass the context for ulp_irq_stop
RDMA/bnxt_re: Allocate dev_attr information dynamically
drivers/infiniband/hw/bnxt_re/bnxt_re.h | 2 +-
drivers/infiniband/hw/bnxt_re/hw_counters.c | 2 +-
drivers/infiniband/hw/bnxt_re/ib_verbs.c | 38 ++++++++++-----------
drivers/infiniband/hw/bnxt_re/main.c | 48 +++++++++++++++++++--------
drivers/infiniband/hw/bnxt_re/qplib_res.c | 7 ++--
drivers/infiniband/hw/bnxt_re/qplib_res.h | 4 +--
drivers/infiniband/hw/bnxt_re/qplib_sp.c | 4 +--
drivers/infiniband/hw/bnxt_re/qplib_sp.h | 3 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 5 ++-
drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h | 2 +-
10 files changed, 67 insertions(+), 48 deletions(-)
--
2.5.5
next reply other threads:[~2025-01-09 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 18:18 Selvin Xavier [this message]
2025-01-09 18:18 ` [PATCH for-next 1/2] RDMA/bnxt_re: Pass the context for ulp_irq_stop Selvin Xavier
2025-01-09 18:18 ` [PATCH for-next 2/2] RDMA/bnxt_re: Allocate dev_attr information dynamically Selvin Xavier
2025-01-14 11:25 ` Leon Romanovsky
2025-01-15 4:03 ` Kalesh Anakkur Purayil
2025-01-14 11:26 ` [PATCH for-next 0/2] RDMA/bnxt_re: Driver update Leon Romanovsky
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=1736446693-6692-1-git-send-email-selvin.xavier@broadcom.com \
--to=selvin.xavier@broadcom.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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