From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: fsverity@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: [GIT PULL] fsverity fixes for v7.0-rc1
Date: Sun, 22 Feb 2026 12:38:43 -0800 [thread overview]
Message-ID: <20260222203843.GD37806@quark> (raw)
The following changes since commit 64275e9fda3702bfb5ab3b95f7c2b9b414667164:
Merge tag 'loongarch-7.0' of git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson (2026-02-14 12:47:15 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fsverity/linux.git tags/fsverity-for-linus
for you to fetch changes up to 693680b9add63dbebb2505a553ff52f8c706c8c0:
fsverity: fix build error by adding fsverity_readahead() stub (2026-02-17 23:11:40 -0800)
----------------------------------------------------------------
- Fix a build error on parisc
- Remove the non-large-folio-aware function fsverity_verify_page()
----------------------------------------------------------------
Eric Biggers (4):
f2fs: remove unnecessary ClearPageUptodate in f2fs_verify_cluster()
f2fs: make f2fs_verify_cluster() partially large-folio-aware
fsverity: remove fsverity_verify_page()
fsverity: fix build error by adding fsverity_readahead() stub
fs/f2fs/compress.c | 11 +++++------
fs/verity/verify.c | 4 ++--
include/linux/fsverity.h | 15 +++++++--------
3 files changed, 14 insertions(+), 16 deletions(-)
next reply other threads:[~2026-02-22 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 20:38 Eric Biggers [this message]
2026-02-22 21:19 ` [f2fs-dev] [GIT PULL] fsverity fixes for v7.0-rc1 pr-tracker-bot
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=20260222203843.GD37806@quark \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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