From: patchwork-bot+netdevbpf@kernel.org
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: andrew.gospodarek@broadcom.com, davem@davemloft.net,
edumazet@google.com, jgg@ziepe.ca, kuba@kernel.org,
leon@kernel.org, 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 v11 0/8] Add Auxiliary driver support
Date: Tue, 07 Feb 2023 06:40:19 +0000 [thread overview]
Message-ID: <167575201929.385.11164394951252164491.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230202033809.3989-1-ajit.khaparde@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Ajit Khaparde <ajit.khaparde@broadcom.com>:
On Wed, 1 Feb 2023 19:38:01 -0800 you 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.
>
> [...]
Here is the summary with links:
- [net-next,v11,1/8] bnxt_en: Add auxiliary driver support
https://git.kernel.org/netdev/net-next/c/d80d88b0dfff
- [net-next,v11,2/8] RDMA/bnxt_re: Use auxiliary driver interface
https://git.kernel.org/netdev/net-next/c/6d758147c7b8
- [net-next,v11,3/8] bnxt_en: Remove usage of ulp_id
https://git.kernel.org/netdev/net-next/c/dafcdf5e2bd0
- [net-next,v11,4/8] bnxt_en: Use direct API instead of indirection
https://git.kernel.org/netdev/net-next/c/63669ab384ea
- [net-next,v11,5/8] bnxt_en: Use auxiliary bus calls over proprietary calls
https://git.kernel.org/netdev/net-next/c/3b65e9456c29
- [net-next,v11,6/8] bnxt_en: Remove struct bnxt access from RoCE driver
https://git.kernel.org/netdev/net-next/c/848dc857c8de
- [net-next,v11,7/8] RDMA/bnxt_re: Remove the sriov config callback
https://git.kernel.org/netdev/net-next/c/a43c26fa2e6c
- [net-next,v11,8/8] bnxt_en: Remove runtime interrupt vector allocation
https://git.kernel.org/netdev/net-next/c/303432211324
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-07 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 3:38 [PATCH net-next v11 0/8] Add Auxiliary driver support Ajit Khaparde
2023-02-02 3:38 ` [PATCH net-next v11 1/8] bnxt_en: Add auxiliary " Ajit Khaparde
2023-02-02 3:38 ` [PATCH net-next v11 2/8] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2023-02-02 3:38 ` [PATCH net-next v11 3/8] bnxt_en: Remove usage of ulp_id Ajit Khaparde
2023-02-02 3:38 ` [PATCH net-next v11 4/8] bnxt_en: Use direct API instead of indirection Ajit Khaparde
2023-02-02 3:38 ` [PATCH net-next v11 5/8] bnxt_en: Use auxiliary bus calls over proprietary calls Ajit Khaparde
2023-02-02 3:38 ` [PATCH net-next v11 6/8] bnxt_en: Remove struct bnxt access from RoCE driver Ajit Khaparde
2023-02-02 3:38 ` [PATCH net-next v11 7/8] RDMA/bnxt_re: Remove the sriov config callback Ajit Khaparde
2023-02-02 3:38 ` [PATCH net-next v11 8/8] bnxt_en: Remove runtime interrupt vector allocation Ajit Khaparde
2023-02-02 3:49 ` [PATCH net-next v11 0/8] Add Auxiliary driver support Jakub Kicinski
2023-02-06 16:58 ` Ajit Khaparde
2023-02-07 6:40 ` patchwork-bot+netdevbpf [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=167575201929.385.11164394951252164491.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=kuba@kernel.org \
--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).