From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: David Howells <dhowells@redhat.com>,
linux-cachefs@redhat.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Reference to non-existing CONFIG_NETFS_FSCACHE
Date: Mon, 8 Jan 2024 11:42:06 +0100 [thread overview]
Message-ID: <CAKXUXMzXN=+hKDPP-RdHKELA_fGA6PcdCj5fXM32qh4Px0Hprg@mail.gmail.com> (raw)
Dear David,
I have seen that you have made some recent changes in netfs now
visible in linux-next.
In commit 62c3b7481b9a ("netfs: Provide a writepages implementation"),
you have added some code that is included under #ifdef
CONFIG_NETFS_FSCACHE, but if I read the code correctly, the actual
intended config here is called CONFIG_FSCACHE. As I am not 100% sure
and this code just appeared on linux-next, I thought I would just
write you a mail rather than sending a one-line RFC patch.
Best regards,
Lukas
next reply other threads:[~2024-01-08 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 10:42 Lukas Bulwahn [this message]
2024-01-08 21:41 ` Reference to non-existing CONFIG_NETFS_FSCACHE David Howells
2024-01-08 23:16 ` Matthew Wilcox
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='CAKXUXMzXN=+hKDPP-RdHKELA_fGA6PcdCj5fXM32qh4Px0Hprg@mail.gmail.com' \
--to=lukas.bulwahn@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).