public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matias Bjørling" <m@bjorling.me>
To: Arnd Bergmann <arnd@arndb.de>, Matias Bjorling <mb@lightnvm.io>
Cc: "Simon A. F. Lund" <slund@cnexlabs.com>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lightnvm: propagate device_add() error code
Date: Fri, 16 Sep 2016 12:19:50 +0200	[thread overview]
Message-ID: <57DBC746.4000509@bjorling.me> (raw)
In-Reply-To: <20160915155325.3009409-1-arnd@arndb.de>

On 09/15/2016 05:53 PM, Arnd Bergmann wrote:
> device_add() may fail, and all callers are supposed to check the
> return value, but one new user in lightnvm doesn't:
>
> drivers/lightnvm/sysfs.c: In function 'nvm_sysfs_register_dev':
> drivers/lightnvm/sysfs.c:184:2: error: ignoring return value of 'device_add', declared with attribute warn_unused_result [-Werror=unused-result]
>
> This changes the caller to propagate any error codes, which avoids
> the warning.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: 38c9e260b9f9 ("lightnvm: expose device geometry through sysfs")
> ---
>   drivers/lightnvm/lightnvm.h | 2 +-
>   drivers/lightnvm/sysfs.c    | 9 ++++++---
>   2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/lightnvm/lightnvm.h b/drivers/lightnvm/lightnvm.h
> index 93f1aacc9f02..305c181509a6 100644
> --- a/drivers/lightnvm/lightnvm.h
> +++ b/drivers/lightnvm/lightnvm.h
> @@ -24,7 +24,7 @@
>   #include <linux/lightnvm.h>
>
>   /* core -> sysfs.c */
> -int nvm_sysfs_register_dev(struct nvm_dev *);
> +int __must_check nvm_sysfs_register_dev(struct nvm_dev *);
>   void nvm_sysfs_unregister_dev(struct nvm_dev *);
>   int nvm_sysfs_register(void);
>   void nvm_sysfs_unregister(void);
> diff --git a/drivers/lightnvm/sysfs.c b/drivers/lightnvm/sysfs.c
> index 72ad089c0269..0338c27ab95a 100644
> --- a/drivers/lightnvm/sysfs.c
> +++ b/drivers/lightnvm/sysfs.c
> @@ -174,6 +174,8 @@ static struct device_type nvm_type = {
>
>   int nvm_sysfs_register_dev(struct nvm_dev *dev)
>   {
> +	int ret;
> +
>   	if (!dev->parent_dev)
>   		return 0;
>
> @@ -181,11 +183,12 @@ int nvm_sysfs_register_dev(struct nvm_dev *dev)
>   	dev_set_name(&dev->dev, "%s", dev->name);
>   	dev->dev.type = &nvm_type;
>   	device_initialize(&dev->dev);
> -	device_add(&dev->dev);
> +	ret = device_add(&dev->dev);
>
> -	blk_mq_register_dev(&dev->dev, dev->q);
> +	if (!ret)
> +		blk_mq_register_dev(&dev->dev, dev->q);
>
> -	return 0;
> +	return ret;
>   }
>
>   void nvm_sysfs_unregister_dev(struct nvm_dev *dev)
>

Thans Arnd. Applied for 4.9.

      reply	other threads:[~2016-09-16 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 15:53 [PATCH] lightnvm: propagate device_add() error code Arnd Bergmann
2016-09-16 10:19 ` Matias Bjørling [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=57DBC746.4000509@bjorling.me \
    --to=m@bjorling.me \
    --cc=arnd@arndb.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@lightnvm.io \
    --cc=slund@cnexlabs.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