From: Jason Gunthorpe <jgg@nvidia.com>
To: Md Haris Iqbal <haris.iqbal@cloud.ionos.com>
Cc: <danil.kipnis@cloud.ionos.com>, <jinpu.wang@cloud.ionos.com>,
<linux-rdma@vger.kernel.org>, <dledford@redhat.com>,
<leon@kernel.org>
Subject: Re: [PATCH v2] RDMA/rtrs-srv: Set .release function for rtrs srv device during device init
Date: Wed, 9 Sep 2020 13:28:42 -0300 [thread overview]
Message-ID: <20200909162842.GA868842@nvidia.com> (raw)
In-Reply-To: <20200907102216.104041-1-haris.iqbal@cloud.ionos.com>
On Mon, Sep 07, 2020 at 03:52:16PM +0530, Md Haris Iqbal wrote:
> The device .release function was not being set during the device
> initialization. This was leading to the below warning, in error cases when
> put_srv was called before device_add was called.
>
> Warning:
>
> Device '(null)' does not have a release() function, it is broken and must
> be fixed. See Documentation/kobject.txt.
>
> So, set the device .release function during device initialization in the
> __alloc_srv() function.
>
> Fixes: baa5b28b7a47 ("RDMA/rtrs-srv: Replace device_register with device_initialize and device_add")
> Signed-off-by: Md Haris Iqbal <haris.iqbal@cloud.ionos.com>
> Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
> Acked-by: Jack Wang <jinpu.wang@cloud.ionos.com>
> ---
> Change in v2:
> Use the complete Fixes line
>
> drivers/infiniband/ulp/rtrs/rtrs-srv-sysfs.c | 8 --------
> drivers/infiniband/ulp/rtrs/rtrs-srv.c | 8 ++++++++
> 2 files changed, 8 insertions(+), 8 deletions(-)
Applied to for-rc thanks
Jason
prev parent reply other threads:[~2020-09-09 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 10:22 [PATCH v2] RDMA/rtrs-srv: Set .release function for rtrs srv device during device init Md Haris Iqbal
2020-09-07 10:33 ` Leon Romanovsky
2020-09-07 12:12 ` Jinpu Wang
2020-09-09 16:28 ` Jason Gunthorpe [this message]
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=20200909162842.GA868842@nvidia.com \
--to=jgg@nvidia.com \
--cc=danil.kipnis@cloud.ionos.com \
--cc=dledford@redhat.com \
--cc=haris.iqbal@cloud.ionos.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=leon@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).