From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Matias Bjørling" <m@bjorling.me>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Simon A. F. Lund" <slund@cnexlabs.com>
Subject: linux-next: build warning after merge of the lightnvm tree
Date: Thu, 15 Sep 2016 13:42:31 +1000 [thread overview]
Message-ID: <20160915134231.144855f3@canb.auug.org.au> (raw)
Hi Matias,
After merging the lightnvm tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/lightnvm/sysfs.c: In function 'nvm_sysfs_register_dev':
drivers/lightnvm/sysfs.c:184:2: warning: ignoring return value of 'device_add', declared with attribute warn_unused_result [-Wunused-result]
device_add(&dev->dev);
^
Introduced by commit
38c9e260b9f9 ("lightnvm: expose device geometry through sysfs")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-09-15 3:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 3:42 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-04 5:52 linux-next: build warning after merge of the lightnvm tree Stephen Rothwell
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=20160915134231.144855f3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m@bjorling.me \
--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;
as well as URLs for NNTP newsgroup(s).