From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Howells <dhowells@redhat•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the fscache tree
Date: Mon, 6 Dec 2021 18:08:36 +1100 [thread overview]
Message-ID: <20211206180836.45cf22cf@canb.auug.org.au> (raw)
In-Reply-To: <20211130152753.6899aa0c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
Hi all,
On Tue, 30 Nov 2021 15:27:53 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the fscache tree, today's linux-next build (arm64 defconfig)
> produced this warning:
>
> fs/9p/vfs_addr.c: In function 'v9fs_release_page':
> fs/9p/vfs_addr.c:140:16: warning: unused variable 'inode' [-Wunused-variable]
> 140 | struct inode *inode = folio_inode(folio);
> | ^~~~~
>
> Introduced by commit
>
> 12b841dc2cfd ("9p: Copy local writes to the cache when writing to the server")
Still getting this ... It will cause build failures for any config with
CONFIG_9P_FSCACHE not set and CONFIG_WERROR set
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-06 7:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 4:27 linux-next: build warning after merge of the fscache tree Stephen Rothwell
2021-12-06 7:08 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-03 9:28 Stephen Rothwell
2021-12-20 11:46 Stephen Rothwell
2021-11-30 5:23 Stephen Rothwell
2021-11-30 6:51 ` Stephen Rothwell
2021-11-30 11:18 ` David Howells
2021-11-30 11:13 ` David Howells
2021-10-05 9:46 Stephen Rothwell
2021-10-21 1:29 ` Stephen Rothwell
2021-10-21 14:32 ` David Howells
2021-10-21 23:15 ` Stephen Rothwell
2021-03-03 6:07 Stephen Rothwell
2021-03-02 22:16 Stephen Rothwell
2021-03-02 22:48 ` David Howells
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=20211206180836.45cf22cf@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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