From: Jason Gunthorpe <jgg@ziepe.ca>
To: Weihang Li <liweihang@huawei.com>
Cc: dledford@redhat.com, leon@kernel.org, linux-rdma@vger.kernel.org,
linuxarm@huawei.com
Subject: Re: [PATCH RFC v2 for-next 3/7] qede: remove invalid notify operation
Date: Wed, 19 Feb 2020 17:04:25 -0400 [thread overview]
Message-ID: <20200219210425.GA31668@ziepe.ca> (raw)
In-Reply-To: <20200204082408.18728-4-liweihang@huawei.com>
On Tue, Feb 04, 2020 at 04:24:04PM +0800, Weihang Li wrote:
> From: Lang Cheng <chenglang@huawei.com>
>
> The qedr notify() will remove the processing of QEDE_UP and QEDE_DOWN,
> so qede no more needs to notify rdma of these two events.
>
> Signed-off-by: Lang Cheng <chenglang@huawei.com>
> drivers/net/ethernet/qlogic/qede/qede_rdma.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/qlogic/qede/qede_rdma.c b/drivers/net/ethernet/qlogic/qede/qede_rdma.c
> index ffabc2d..0493279 100644
> +++ b/drivers/net/ethernet/qlogic/qede/qede_rdma.c
> @@ -145,8 +145,6 @@ void qede_rdma_dev_remove(struct qede_dev *edev, bool recovery)
>
> static void _qede_rdma_dev_open(struct qede_dev *edev)
> {
> - if (qedr_drv && edev->rdma_info.qedr_dev && qedr_drv->notify)
> - qedr_drv->notify(edev->rdma_info.qedr_dev, QEDE_UP);
> }
>
> static void qede_rdma_dev_open(struct qede_dev *edev)
> @@ -161,8 +159,6 @@ static void qede_rdma_dev_open(struct qede_dev *edev)
>
> static void _qede_rdma_dev_close(struct qede_dev *edev)
> {
> - if (qedr_drv && edev->rdma_info.qedr_dev && qedr_drv->notify)
> - qedr_drv->notify(edev->rdma_info.qedr_dev, QEDE_DOWN);
> }
Leaving empty functions behind? Why?
I'm getting the feeling that this series is inside out or
backwards something. This change should not happen until the rdma
driver stops consuming these events
Jason
next prev parent reply other threads:[~2020-02-19 21:04 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 [this message]
2020-02-20 4:18 ` Lang Cheng
2020-02-04 8:24 ` [PATCH RFC v2 for-next 4/7] RDMA/qedr: remove deliver net device event Weihang Li
2020-02-04 8:24 ` [PATCH RFC v2 for-next 5/7] RDMA/vmw_pvrdma: " 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=20200219210425.GA31668@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liweihang@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).