linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Weihang Li <liweihang@huawei.com>
To: <dledford@redhat.com>, <jgg@ziepe.ca>
Cc: <leon@kernel.org>, <linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: [PATCH RFC v2 for-next 4/7] RDMA/qedr: remove deliver net device event
Date: Tue, 4 Feb 2020 16:24:05 +0800	[thread overview]
Message-ID: <20200204082408.18728-5-liweihang@huawei.com> (raw)
In-Reply-To: <20200204082408.18728-1-liweihang@huawei.com>

From: Lang Cheng <chenglang@huawei.com>

The code that handles the link event of the net device has been moved into
the core, and the related processing should been removed from the provider
driver.

Signed-off-by: Lang Cheng <chenglang@huawei.com>
---
 drivers/infiniband/hw/qedr/main.c | 19 -------------------
 1 file changed, 19 deletions(-)

diff --git a/drivers/infiniband/hw/qedr/main.c b/drivers/infiniband/hw/qedr/main.c
index dcdc85a..d85894b 100644
--- a/drivers/infiniband/hw/qedr/main.c
+++ b/drivers/infiniband/hw/qedr/main.c
@@ -957,24 +957,11 @@ static void qedr_remove(struct qedr_dev *dev)
 	ib_dealloc_device(&dev->ibdev);
 }
 
-static void qedr_close(struct qedr_dev *dev)
-{
-	if (test_and_clear_bit(QEDR_ENET_STATE_BIT, &dev->enet_state))
-		qedr_ib_dispatch_event(dev, QEDR_PORT, IB_EVENT_PORT_ERR);
-}
-
 static void qedr_shutdown(struct qedr_dev *dev)
 {
-	qedr_close(dev);
 	qedr_remove(dev);
 }
 
-static void qedr_open(struct qedr_dev *dev)
-{
-	if (!test_and_set_bit(QEDR_ENET_STATE_BIT, &dev->enet_state))
-		qedr_ib_dispatch_event(dev, QEDR_PORT, IB_EVENT_PORT_ACTIVE);
-}
-
 static void qedr_mac_address_change(struct qedr_dev *dev)
 {
 	union ib_gid *sgid = &dev->sgid_tbl[0];
@@ -1014,12 +1001,6 @@ static void qedr_mac_address_change(struct qedr_dev *dev)
 static void qedr_notify(struct qedr_dev *dev, enum qede_rdma_event event)
 {
 	switch (event) {
-	case QEDE_UP:
-		qedr_open(dev);
-		break;
-	case QEDE_DOWN:
-		qedr_close(dev);
-		break;
 	case QEDE_CLOSE:
 		qedr_shutdown(dev);
 		break;
-- 
2.8.1



  parent reply	other threads:[~2020-02-04  8:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04  8:24 [PATCH RFC v2 for-next 0/7] ib core support to send ib port link event Weihang Li
2020-02-04  8:24 ` [PATCH RFC v2 for-next 1/7] RDMA/core: add inactive attribute of ib_port_cache Weihang Li
2020-02-19 21:01   ` Jason Gunthorpe
2020-02-20  3:19     ` Lang Cheng
2020-02-20  6:40       ` Leon Romanovsky
2020-02-04  8:24 ` [PATCH RFC v2 for-next 2/7] RDMA/mlx5: remove deliver net device event Weihang Li
2020-02-19 21:03   ` Jason Gunthorpe
2020-02-04  8:24 ` [PATCH RFC v2 for-next 3/7] qede: remove invalid notify operation Weihang Li
2020-02-19 21:04   ` Jason Gunthorpe
2020-02-20  4:18     ` Lang Cheng
2020-02-04  8:24 ` Weihang Li [this message]
2020-02-04  8:24 ` [PATCH RFC v2 for-next 5/7] RDMA/vmw_pvrdma: remove deliver net device event Weihang Li
2020-02-04  8:24 ` [PATCH RFC v2 for-next 6/7] RDMA/core: support send port event Weihang Li
2020-02-19 21:07   ` Jason Gunthorpe
2020-02-20  8:48     ` Lang Cheng
2020-02-04  8:24 ` [PATCH RFC v2 for-next 7/7] RDMA/core: report link status when register and deregister ib device Weihang Li

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=20200204082408.18728-5-liweihang@huawei.com \
    --to=liweihang@huawei.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.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).