From: Selvin Xavier <selvin.xavier@broadcom.com>
To: dledford@redhat.com, jgg@mellanox.com
Cc: linux-rdma@vger.kernel.org, Selvin Xavier <selvin.xavier@broadcom.com>
Subject: [PATCH for-next v3 0/2] RDMA/bnxt_re driver update
Date: Tue, 25 Feb 2020 21:09:52 -0800 [thread overview]
Message-ID: <1582693794-23373-1-git-send-email-selvin.xavier@broadcom.com> (raw)
Includes code refactoring in the device init/deinit path and
use the new driver unregistration APIs.
Please apply to for-next.
v2 -> v3:
- Droped the patch which was adding more state macros
- To prevent addition of any device during driver removal,
unregister netdev notifier and delete the driver's workqueu
before calling ib_unregister_driver
v1-> v2:
- Remove the patches 1,2 and 6 from the v1 series.
They are already merged.
- Added ASSERT_RTNL instead of comment in Patch 2
- For Patch 3, explicitly queue the removal of the VF devices
before calling ib_unregister_driver. This can avoid command
timeouts seen, if the PFs gets removed before the VFs.
Previous discussion - https://patchwork.kernel.org/patch/11260013/
Selvin Xavier (2):
RDMA/bnxt_re: Refactor device add/remove functionalities
RDMA/bnxt_re: Use driver_unregister and unregistration API
drivers/infiniband/hw/bnxt_re/main.c | 209 +++++++++++++++++------------------
1 file changed, 104 insertions(+), 105 deletions(-)
--
2.5.5
next reply other threads:[~2020-02-26 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 5:09 Selvin Xavier [this message]
2020-02-26 5:09 ` [PATCH for-next v3 1/2] RDMA/bnxt_re: Refactor device add/remove functionalities Selvin Xavier
2020-02-26 5:28 ` Parav Pandit
2020-02-26 7:52 ` Selvin Xavier
2020-02-26 5:09 ` [PATCH for-next v3 2/2] RDMA/bnxt_re: Use driver_unregister and unregistration API Selvin Xavier
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=1582693794-23373-1-git-send-email-selvin.xavier@broadcom.com \
--to=selvin.xavier@broadcom.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--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