From: Jason Gunthorpe <jgg@ziepe.ca>
To: YueHaibing <yuehaibing@huawei.com>
Cc: mike.marciniszyn@intel.com, dennis.dalessandro@intel.com,
dledford@redhat.com, sadanand.warrier@intel.com,
grzegorz.andrejczuk@intel.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, dan.carpenter@oracle.com,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] IB/hfi1: Use free_netdev() in hfi1_netdev_free()
Date: Wed, 03 Jun 2020 00:36:06 +0000 [thread overview]
Message-ID: <20200603003606.GA132773@ziepe.ca> (raw)
In-Reply-To: <20200602061635.31224-1-yuehaibing@huawei.com>
On Tue, Jun 02, 2020 at 02:16:35PM +0800, YueHaibing wrote:
> dummy_netdev shold be freed by free_netdev() instead of
> kfree(). Also remove unneeded variable 'priv'
>
> Fixes: 4730f4a6c6b2 ("IB/hfi1: Activate the dummy netdev")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> Reported-by: kbuild test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Reviewed-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
> ---
> drivers/infiniband/hw/hfi1/netdev_rx.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
Applied to for-next, thanks
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: YueHaibing <yuehaibing@huawei.com>
Cc: mike.marciniszyn@intel.com, dennis.dalessandro@intel.com,
dledford@redhat.com, sadanand.warrier@intel.com,
grzegorz.andrejczuk@intel.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, dan.carpenter@oracle.com,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] IB/hfi1: Use free_netdev() in hfi1_netdev_free()
Date: Tue, 2 Jun 2020 21:36:06 -0300 [thread overview]
Message-ID: <20200603003606.GA132773@ziepe.ca> (raw)
In-Reply-To: <20200602061635.31224-1-yuehaibing@huawei.com>
On Tue, Jun 02, 2020 at 02:16:35PM +0800, YueHaibing wrote:
> dummy_netdev shold be freed by free_netdev() instead of
> kfree(). Also remove unneeded variable 'priv'
>
> Fixes: 4730f4a6c6b2 ("IB/hfi1: Activate the dummy netdev")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> Reported-by: kbuild test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Reviewed-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
> ---
> drivers/infiniband/hw/hfi1/netdev_rx.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
Applied to for-next, thanks
Jason
next prev parent reply other threads:[~2020-06-03 0:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 7:59 [PATCH -next] IB/hfi1: Remove set but not used variable 'priv' YueHaibing
2020-05-28 7:59 ` YueHaibing
2020-05-28 11:25 ` Marciniszyn, Mike
2020-06-01 13:45 ` Dennis Dalessandro
2020-06-01 13:45 ` Dennis Dalessandro
2020-06-01 13:56 ` Jason Gunthorpe
2020-06-01 13:56 ` Jason Gunthorpe
2020-06-02 0:59 ` Yuehaibing
2020-06-02 0:59 ` Yuehaibing
2020-06-02 6:16 ` [PATCH -next] IB/hfi1: Use free_netdev() in hfi1_netdev_free() YueHaibing
2020-06-02 6:16 ` YueHaibing
2020-06-02 15:30 ` Dennis Dalessandro
2020-06-02 15:30 ` Dennis Dalessandro
2020-06-02 18:38 ` Dan Carpenter
2020-06-02 18:38 ` Dan Carpenter
2020-06-03 0:36 ` Jason Gunthorpe [this message]
2020-06-03 0:36 ` Jason Gunthorpe
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=20200603003606.GA132773@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dan.carpenter@oracle.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=grzegorz.andrejczuk@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=sadanand.warrier@intel.com \
--cc=yuehaibing@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.