From: Jeff Layton <jlayton@kernel.org>
To: David Howells <dhowells@redhat.com>,
Christian Brauner <christian@brauner.io>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Dominique Martinet <asmadeus@codewreck.org>
Cc: Steve French <smfrench@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
Marc Dionne <marc.dionne@auristor.com>,
Paulo Alcantara <pc@manguebit.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Tom Talpey <tom@talpey.com>,
Eric Van Hensbergen <ericvh@kernel.org>,
Ilya Dryomov <idryomov@gmail.com>,
linux-cachefs@redhat.com, linux-afs@lists.infradead.org,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
ceph-devel@vger.kernel.org, v9fs@lists.linux.dev,
linux-erofs@lists.ozlabs.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] netfs, afs, erofs, cifs: Don't use certain internal folio_*() functions
Date: Tue, 09 Jan 2024 13:42:53 -0500 [thread overview]
Message-ID: <8f28f3276b0ae3ecac6875bed4807db2ebd5a425.camel@kernel.org> (raw)
In-Reply-To: <20240109180117.1669008-1-dhowells@redhat.com>
On Tue, 2024-01-09 at 18:01 +0000, David Howells wrote:
> Hi Christian, Willy,
>
> Here are some patches that replace the use of folio_index(),
> folio_mapping() and folio_file_mapping() in some filesystem code. I'll add
> them to my netfs-lib branch.
>
> David
>
> David Howells (4):
> netfs: Don't use certain internal folio_*() functions
> afs: Don't use certain internal folio_*() functions
> erofs: Don't use certain internal folio_*() functions
> cifs: Don't use certain internal folio_*() functions
>
> fs/afs/dir.c | 10 +++++-----
> fs/erofs/fscache.c | 6 +++---
> fs/netfs/buffered_read.c | 12 ++++++------
> fs/netfs/buffered_write.c | 10 +++++-----
> fs/netfs/io.c | 2 +-
> fs/netfs/misc.c | 2 +-
> fs/smb/client/file.c | 10 +++++-----
> 7 files changed, 26 insertions(+), 26 deletions(-)
>
Looks like a fairly straightforward cleanup. Aside from the changelog
comments on patch #1:
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-01-09 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 18:01 [PATCH 0/4] netfs, afs, erofs, cifs: Don't use certain internal folio_*() functions David Howells
2024-01-09 18:01 ` [PATCH 1/4] netfs: " David Howells
2024-01-09 18:41 ` Jeff Layton
2024-01-10 17:25 ` John Stoffel
2024-01-09 18:01 ` [PATCH 2/4] afs: " David Howells
2024-01-09 18:01 ` [PATCH 3/4] erofs: " David Howells
2024-01-09 18:11 ` Gao Xiang
2024-01-15 8:34 ` [PATCH v2 " Gao Xiang
2024-01-09 18:01 ` [PATCH 4/4] cifs: " David Howells
2024-01-09 18:42 ` Jeff Layton [this message]
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=8f28f3276b0ae3ecac6875bed4807db2ebd5a425.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=ceph-devel@vger.kernel.org \
--cc=christian@brauner.io \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=idryomov@gmail.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
--cc=v9fs@lists.linux.dev \
--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 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).