From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Jan Kara <jack@suse.cz>, Matthew Wilcox <mawilcox@microsoft.com>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: build warning after merge of the file-locks tree
Date: Wed, 21 Jun 2017 17:11:19 +1000 [thread overview]
Message-ID: <20170621171119.65a81101@canb.auug.org.au> (raw)
In-Reply-To: <20170621103052.2eb33b59@canb.auug.org.au>
Hi Jeff,
On Wed, 21 Jun 2017 10:30:52 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the file-locks tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/jfs/jfs_metapage.c: In function 'force_metapage':
> fs/jfs/jfs_metapage.c:714:2: warning: ignoring return value of 'write_one_page', declared with attribute warn_unused_result [-Wunused-result]
> write_one_page(page);
> ^
> fs/jfs/jfs_metapage.c: In function 'release_metapage':
> fs/jfs/jfs_metapage.c:759:4: warning: ignoring return value of 'write_one_page', declared with attribute warn_unused_result [-Wunused-result]
> write_one_page(page);
> ^
>
> Introduced by commit
>
> ee6b2b8e0a8f ("mm: drop "wait" parameter from write_one_page()")
This is fixed up by commit
f0423ddc1cf6 ("JFS: do not ignore return code from write_one_page()")
in the akpm-current tree.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-06-21 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 0:30 linux-next: build warning after merge of the file-locks tree Stephen Rothwell
2017-06-21 7:11 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-21 0:30 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=20170621171119.65a81101@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=ross.zwisler@linux.intel.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