From: Matthew Wilcox <willy@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-cachefs@redhat.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reference to non-existing CONFIG_NETFS_FSCACHE
Date: Mon, 8 Jan 2024 23:16:28 +0000 [thread overview]
Message-ID: <ZZyCTPz+uuvgjPIL@casper.infradead.org> (raw)
In-Reply-To: <1542013.1704750095@warthog.procyon.org.uk>
On Mon, Jan 08, 2024 at 09:41:35PM +0000, David Howells wrote:
> netfs_writepages_begin() has the wait on the fscache folio conditional on
> CONFIG_NETFS_FSCACHE - which doesn't exist.
>
> Fix it to be conditional on CONFIG_FSCACHE instead.
Why is it conditional at all? Why don't we have a stub function if
CONFIG_FSCACHE is not defined?
next prev parent reply other threads:[~2024-01-08 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 10:42 Reference to non-existing CONFIG_NETFS_FSCACHE Lukas Bulwahn
2024-01-08 21:41 ` David Howells
2024-01-08 23:16 ` Matthew Wilcox [this message]
2024-01-09 11:08 ` 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=ZZyCTPz+uuvgjPIL@casper.infradead.org \
--to=willy@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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).