From: Christian Brauner <brauner@kernel.org>
To: Phillip Lougher <phillip@squashfs.org.uk>
Cc: Christian Brauner <brauner@kernel.org>,
willy@infradead.org, lizetao1@huawei.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/4] Squashfs: Update code to not use page->index
Date: Mon, 19 Aug 2024 14:09:35 +0200 [thread overview]
Message-ID: <20240819-serpentinen-thema-e13d7625bbfa@brauner> (raw)
In-Reply-To: <20240818235847.170468-1-phillip@squashfs.org.uk>
On Mon, 19 Aug 2024 00:58:43 +0100, Phillip Lougher wrote:
> In the near future page->index will be removed [1]. Any code which
> still uses page->index needs to be updated.
>
> This patch-set contains 4 patches which updates most of the code in
> Squashfs. The exceptions are functions which have been fixed in
> recent patches [2] & [3].
>
> [...]
Applied to the vfs.folio branch of the vfs/vfs.git tree.
Patches in the vfs.folio branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.folio
[1/4] Squashfs: Update page_actor to not use page->index
https://git.kernel.org/vfs/vfs/c/2258e22f05af
[2/4] Squashfs: Update squashfs_readahead() to not use page->index
https://git.kernel.org/vfs/vfs/c/6f09ffb1f4fa
[3/4] Squashfs: Update squashfs_readpage_block() to not use page->index
https://git.kernel.org/vfs/vfs/c/7f73fcde4d93
[4/4] Squashfs: Rewrite and update squashfs_readahead_fragment() to not use page->index
https://git.kernel.org/vfs/vfs/c/fd54fa6efe0d
prev parent reply other threads:[~2024-08-19 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 23:58 [PATCH 0/4] Squashfs: Update code to not use page->index Phillip Lougher
2024-08-18 23:58 ` [PATCH 1/4] Squashfs: Update page_actor " Phillip Lougher
2024-08-18 23:58 ` [PATCH 2/4] Squashfs: Update squashfs_readahead() " Phillip Lougher
2024-08-18 23:58 ` [PATCH 3/4] Squashfs: Update squashfs_readpage_block() " Phillip Lougher
2024-08-18 23:58 ` [PATCH 4/4] Squashfs: Rewrite and update squashfs_readahead_fragment() " Phillip Lougher
2024-08-19 12:09 ` Christian Brauner [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=20240819-serpentinen-thema-e13d7625bbfa@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizetao1@huawei.com \
--cc=phillip@squashfs.org.uk \
--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