From: Leon Romanovsky <leon@kernel.org>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: michael.chan@broadcom.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jgg@ziepe.ca, selvin.xavier@broadcom.com,
linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH 2/2] RDMA/bnxt_re: Use auxiliary driver interface
Date: Mon, 25 Jul 2022 15:15:19 +0300 [thread overview]
Message-ID: <Yt6JV0Vs7nSnI8KB@unreal> (raw)
In-Reply-To: <20220724231458.93830-3-ajit.khaparde@broadcom.com>
On Sun, Jul 24, 2022 at 04:14:58PM -0700, Ajit Khaparde wrote:
> Use auxiliary driver interface for driver load, unload ROCE driver.
> The driver does not need to register the interface using the netdev
> notifier anymore. Removed the bnxt_re_dev_list which is not needed.
> Currently probe, remove and shutdown ops have been implemented for
> the auxiliary device.
>
> BUG: DCSG01157556
> Change-Id: Ice54f076c1c4fc26d4ee7e77a5dcd1ca21cf4cd0
Please remove the lines above.
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> drivers/infiniband/hw/bnxt_re/bnxt_re.h | 9 +-
> drivers/infiniband/hw/bnxt_re/main.c | 405 +++++++-----------
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 64 ---
> drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 65 +++
> drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h | 3 +
> 5 files changed, 232 insertions(+), 314 deletions(-)
<...>
> +static DEFINE_IDA(bnxt_aux_dev_ids);
> +
> static int bnxt_register_dev(struct bnxt_en_dev *edev, unsigned int ulp_id,
> struct bnxt_ulp_ops *ulp_ops, void *handle)
I would expect that almost all code in bnxt_ulp.c will go after this change.
Thanks
next prev parent reply other threads:[~2022-07-25 12:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 23:14 [PATCH 0/2] Add Auxiliary driver support Ajit Khaparde
2022-07-24 23:14 ` [PATCH 1/2] net/bnxt: Add auxiliary " Ajit Khaparde
2022-08-02 12:50 ` kernel test robot
2022-07-24 23:14 ` [PATCH 2/2] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2022-07-25 12:15 ` Leon Romanovsky [this message]
2022-07-26 4:58 ` Ajit Khaparde
2022-07-26 5:36 ` Leon Romanovsky
2022-07-26 14:31 ` Ajit Khaparde
2022-10-25 17:31 ` [PATCH v2 0/6] Add Auxiliary driver support Ajit Khaparde
2022-10-25 17:31 ` [PATCH v2 1/6] bnxt_en: Add auxiliary " Ajit Khaparde
2022-10-25 17:31 ` [PATCH v2 2/6] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2022-10-26 9:24 ` Leon Romanovsky
2022-10-26 15:58 ` Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 0/6] Add Auxiliary driver support Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 1/6] bnxt_en: Add auxiliary " Ajit Khaparde
2022-11-08 7:21 ` kernel test robot
2022-11-04 16:27 ` [PATCH v3 2/6] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 3/6] bnxt_en: Remove usage of ulp_id Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 4/6] bnxt_en: Use direct API instead of indirection Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 5/6] bnxt_en: Use auxiliary bus calls over proprietary calls Ajit Khaparde
2022-11-07 6:41 ` Leon Romanovsky
2022-11-09 18:45 ` Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 6/6] bnxt_en: Remove struct bnxt access from RoCE driver Ajit Khaparde
2022-11-07 6:37 ` [PATCH v3 0/6] Add Auxiliary driver support Leon Romanovsky
2022-11-07 16:06 ` Jakub Kicinski
2022-11-07 17:26 ` Leon Romanovsky
2022-11-07 18:21 ` Ajit Khaparde
2022-10-25 17:31 ` [PATCH v2 3/6] bnxt_en: Remove usage of ulp_id Ajit Khaparde
2022-10-26 0:57 ` kernel test robot
2022-10-25 17:31 ` [PATCH v2 4/6] bnxt_en: Use direct API instead of indirection Ajit Khaparde
2022-10-27 17:56 ` kernel test robot
2022-10-25 17:31 ` [PATCH v2 5/6] bnxt_en: Use auxiliary bus calls over proprietary calls Ajit Khaparde
2022-10-25 21:18 ` kernel test robot
2022-10-26 3:21 ` kernel test robot
2022-10-25 17:31 ` [PATCH v2 6/6] bnxt_en: Remove struct bnxt access from RoCE driver 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=Yt6JV0Vs7nSnI8KB@unreal \
--to=leon@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@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).