From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: linux-next: build warning after merge of the btrfs tree
Date: Wed, 12 Feb 2020 17:03:41 +0100 [thread overview]
Message-ID: <20200212160341.GL2902@suse.cz> (raw)
In-Reply-To: <20200212091028.718ca6dc@canb.auug.org.au>
On Wed, Feb 12, 2020 at 09:10:28AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the btrfs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/btrfs/volumes.c: In function 'btrfs_scratch_superblocks':
> fs/btrfs/volumes.c:7338:3: warning: ignoring return value of 'write_one_page', declared with attribute warn_unused_result [-Wunused-result]
> 7338 | write_one_page(page);
> | ^~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
> d19ec014a46b ("btrfs: use the page-cache for super block reading")
Known and fix is in the patchset revision that will be in the next
for-next branch update. Thanks.
next prev parent reply other threads:[~2020-02-12 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 22:10 linux-next: build warning after merge of the btrfs tree Stephen Rothwell
2020-02-12 16:03 ` David Sterba [this message]
2020-02-20 22:32 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2020-02-23 22:57 Stephen Rothwell
2020-02-24 14:34 ` David Sterba
2020-08-25 0:45 Stephen Rothwell
2021-01-26 23:18 Stephen Rothwell
2021-01-27 19:46 ` David Sterba
2022-07-22 1:03 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=20200212160341.GL2902@suse.cz \
--to=dsterba@suse.cz \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.