From: Jakub Kicinski <kuba@kernel.org>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, leon@kernel.org
Cc: andrew.gospodarek@broadcom.com, davem@davemloft.net,
edumazet@google.com, jgg@ziepe.ca, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, michael.chan@broadcom.com,
netdev@vger.kernel.org, pabeni@redhat.com,
selvin.xavier@broadcom.com, gregkh@linuxfoundation.org
Subject: Re: [PATCH net-next v9 0/8] Add Auxiliary driver support
Date: Tue, 31 Jan 2023 21:12:28 -0800 [thread overview]
Message-ID: <20230131211228.78dae343@kernel.org> (raw)
In-Reply-To: <20230131052557.99119-1-ajit.khaparde@broadcom.com>
On Mon, 30 Jan 2023 21:25:49 -0800 Ajit Khaparde wrote:
> Add auxiliary device driver for Broadcom devices.
> The bnxt_en driver will register and initialize an aux device
> if RDMA is enabled in the underlying device.
> The bnxt_re driver will then probe and initialize the
> RoCE interfaces with the infiniband stack.
>
> We got rid of the bnxt_en_ops which the bnxt_re driver used to
> communicate with bnxt_en.
> Similarly We have tried to clean up most of the bnxt_ulp_ops.
> In most of the cases we used the functions and entry points provided
> by the auxiliary bus driver framework.
> And now these are the minimal functions needed to support the functionality.
>
> We will try to work on getting rid of the remaining if we find any
> other viable option in future.
Better :)
Leon, looks good to you as well?
Note to DaveM/self - this needs to be pulled rather than applied:
> The following are changes since commit 90e8ca0abb05ada6c1e2710eaa21688dafca26f2
> Merge branch 'devlink-next'
> and are available in the git repository at:
> https://github.com/ajitkhaparde1/net-next/tree/aux-bus-v9
next prev parent reply other threads:[~2023-02-01 5:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 5:25 [PATCH net-next v9 0/8] Add Auxiliary driver support Ajit Khaparde
2023-01-31 5:25 ` [PATCH net-next v9 1/8] bnxt_en: Add auxiliary " Ajit Khaparde
2023-01-31 5:25 ` [PATCH net-next v9 2/8] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2023-01-31 5:25 ` [PATCH net-next v9 3/8] bnxt_en: Remove usage of ulp_id Ajit Khaparde
2023-01-31 5:25 ` [PATCH net-next v9 4/8] bnxt_en: Use direct API instead of indirection Ajit Khaparde
2023-01-31 5:25 ` [PATCH net-next v9 5/8] bnxt_en: Use auxiliary bus calls over proprietary calls Ajit Khaparde
2023-01-31 5:25 ` [PATCH net-next v9 6/8] bnxt_en: Remove struct bnxt access from RoCE driver Ajit Khaparde
2023-01-31 5:25 ` [PATCH net-next v9 7/8] RDMA/bnxt_re: Remove the sriov config callback Ajit Khaparde
2023-01-31 5:25 ` [PATCH net-next v9 8/8] bnxt_en: Remove runtime interrupt vector allocation Ajit Khaparde
2023-02-01 5:12 ` Jakub Kicinski [this message]
2023-02-01 8:38 ` [PATCH net-next v9 0/8] Add Auxiliary driver support Leon Romanovsky
2023-02-01 16:56 ` Ajit Khaparde
2023-02-01 18:56 ` Jakub Kicinski
2023-02-01 18:58 ` Ajit Khaparde
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=20230131211228.78dae343@kernel.org \
--to=kuba@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).