From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shaohua Li <shli@kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Song Liu <songliubraving@fb.com>
Subject: linux-next: build warning after merge of the md tree
Date: Wed, 9 Aug 2017 13:14:40 +1000 [thread overview]
Message-ID: <20170809131440.00ff9b04@canb.auug.org.au> (raw)
Hi Shaohua,
After merging the md tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
drivers/md/raid5-cache.c: In function 'r5c_journal_mode_show':
drivers/md/raid5-cache.c:2535:2: warning: ignoring return value of 'mddev_lock', declared with attribute warn_unused_result [-Wunused-result]
mddev_lock(mddev);
^
Introduced by commit
7f7abe0ec5bb ("md/r5cache: call mddev_lock/unlock() in r5c_journal_mode_show")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-08-09 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 3:14 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-28 4:40 linux-next: build warning after merge of the md tree Stephen Rothwell
2017-03-28 8:17 ` Ming Lei
2017-03-28 15:49 ` Shaohua Li
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=20170809131440.00ff9b04@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=shli@kernel.org \
--cc=songliubraving@fb.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).