From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the driver-core tree
Date: Wed, 9 Sep 2020 17:23:17 +1000 [thread overview]
Message-ID: <20200909172317.170984de@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
Hi all,
After merging the driver-core tree, today's linux-next build produced
this warning:
drivers/mmc/host/davinci_mmc.c: In function 'davinci_mmcsd_probe':
drivers/mmc/host/davinci_mmc.c:1243:4: warning: ignoring return value of 'dev_err_probe' declared with attribute 'warn_unused_result' [-Wunused-result]
1243 | dev_err_probe(&pdev->dev, ret,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1244 | "could not parse of data\n");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Introduced by commit
e1f82a0dcf38 ("driver core: Annotate dev_err_probe() with __must_check")
interacting with commit
3a35e7e1bd50 ("mmc: davinci: Simplify with dev_err_probe()")
from the mmc tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-09-09 7:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 7:23 Stephen Rothwell [this message]
2020-09-09 7:40 ` linux-next: build warning after merge of the driver-core tree Greg KH
-- strict thread matches above, loose matches on Subject: below --
2023-03-27 1:03 Stephen Rothwell
2023-03-27 7:31 ` Greg KH
2023-02-20 5:31 Stephen Rothwell
2023-02-20 7:26 ` Qi Zheng
2023-02-20 7:31 ` Greg KH
2023-02-20 9:49 ` Bagas Sanjaya
2023-02-20 10:15 ` Qi Zheng
2023-02-20 10:50 ` Greg KH
2023-02-20 11:01 ` Qi Zheng
2022-05-01 22:36 Stephen Rothwell
2021-12-06 8:30 Stephen Rothwell
2021-12-06 12:53 ` Heiko Carstens
2021-12-07 10:23 ` Greg KH
2019-08-05 3:04 Stephen Rothwell
2019-08-05 4:56 ` Stephen Rothwell
2019-08-06 0:03 ` Saravana Kannan
2019-08-01 5:05 Stephen Rothwell
2019-08-01 6:10 ` Greg KH
2019-07-04 6:24 Stephen Rothwell
2019-07-04 8:21 ` Greg KH
2019-07-04 6:17 Stephen Rothwell
2019-07-04 6:30 ` Greg KH
2015-10-07 4:51 Stephen Rothwell
2015-10-07 6:40 ` Viresh Kumar
2015-10-07 21:48 ` Rafael J. Wysocki
2015-10-07 22:04 ` Stephen Rothwell
2015-10-07 22:47 ` Rafael J. Wysocki
2015-10-08 7:09 ` Viresh Kumar
2015-10-08 20:30 ` Rafael J. Wysocki
2015-10-09 5:36 ` Stephen Rothwell
2015-10-09 6:31 ` Viresh Kumar
2015-10-09 20:49 ` Rafael J. Wysocki
2015-10-09 6:37 ` Viresh Kumar
2013-06-25 8:33 Stephen Rothwell
2013-06-25 12:00 ` Ming Lei
2011-02-21 6:02 Stephen Rothwell
2011-02-21 6:32 ` Greg KH
2011-02-21 20:18 ` Ilya Yanok
2011-02-21 5:37 Stephen Rothwell
2011-02-21 5:50 ` Stephen Rothwell
2011-02-21 6:31 ` Greg KH
2011-03-17 23:10 ` Stephen Rothwell
2010-09-02 3:18 Stephen Rothwell
2010-09-02 3:29 ` Greg KH
2010-09-02 10:14 ` Thomas Renninger
2010-09-02 19:59 ` Greg KH
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=20200909172317.170984de@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=greg@kroah.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ulf.hansson@linaro.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).