From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trondmy@kernel.org>
Cc: Anna Schumaker <anna@kernel.org>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Mike Snitzer <snitzer@kernel.org>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v4 1/3] filemap: Add a helper for filesystems implementing dropbehind
Date: Tue, 19 Aug 2025 07:25:37 -0700 [thread overview]
Message-ID: <aKSJYTJdYHDgsHwx@infradead.org> (raw)
In-Reply-To: <ee863d320994130efcccf132212ec0e23f4582ca.1755612705.git.trond.myklebust@hammerspace.com>
On Tue, Aug 19, 2025 at 07:18:30AM -0700, Trond Myklebust wrote:
> +EXPORT_SYMBOL(folio_end_dropbehind);
This really should be a EXPORT_SYMBOL_GPL like for any other linux-only
functionality. Same for the next patch.
next prev parent reply other threads:[~2025-08-19 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 14:18 [PATCH v4 0/3] Initial NFS client support for RWF_DONTCACHE Trond Myklebust
2025-08-19 14:18 ` [PATCH v4 1/3] filemap: Add a helper for filesystems implementing dropbehind Trond Myklebust
2025-08-19 14:25 ` Christoph Hellwig [this message]
2025-08-19 14:18 ` [PATCH v4 2/3] filemap: Add a version of folio_end_writeback that ignores dropbehind Trond Myklebust
2025-08-19 14:18 ` [PATCH v4 3/3] NFS: Enable use of the RWF_DONTCACHE flag on the NFS client Trond Myklebust
2025-09-06 16:48 ` [PATCH v5 0/3] Initial NFS client support for RWF_DONTCACHE Trond Myklebust
2025-09-10 1:53 ` Trond Myklebust
2025-09-06 16:48 ` [PATCH v5 1/3] filemap: Add a helper for filesystems implementing dropbehind Trond Myklebust
2025-09-10 1:53 ` Trond Myklebust
2025-09-06 16:48 ` [PATCH v5 2/3] filemap: Add a version of folio_end_writeback that ignores dropbehind Trond Myklebust
2025-09-10 1:53 ` Trond Myklebust
2025-09-06 16:48 ` [PATCH v5 3/3] NFS: Enable use of the RWF_DONTCACHE flag on the NFS client Trond Myklebust
2025-09-10 1:53 ` Trond Myklebust
2025-09-10 1:59 ` [PATCH v5 0/3] Initial NFS client support for RWF_DONTCACHE Trond Myklebust
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=aKSJYTJdYHDgsHwx@infradead.org \
--to=hch@infradead.org \
--cc=anna@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=snitzer@kernel.org \
--cc=trondmy@kernel.org \
--cc=willy@infradead.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 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.