From: Eric Biggers <ebiggers@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
fsverity@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>,
Andrey Albershteyn <aalbersh@redhat.com>,
"Darrick J. Wong" <djwong@kernel.org>,
David Sterba <dsterba@suse.com>, Jan Kara <jack@suse.cz>
Subject: Re: [GIT PULL] fsverity updates for 7.0
Date: Thu, 12 Feb 2026 09:38:02 -0800 [thread overview]
Message-ID: <20260212173802.GA2269@sol> (raw)
In-Reply-To: <20260212101143.GA7951@lst.de>
On Thu, Feb 12, 2026 at 11:11:43AM +0100, Christoph Hellwig wrote:
> Note that this had a merge conflict in linux-next. So unless that
> went away, it needs a merge resolution like:
>
> https://lore.kernel.org/fsverity/20260203053604.GC15956@lst.de/T/#m291294c1f6b7368d3c426ee47e6d23dc854b3ba6
It will be needed after both this pull request and the f2fs pull request
are merged. Currently, the f2fs pull request hasn't been sent yet.
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Christoph Hellwig <hch@lst.de>
Cc: fsverity@lists.linux.dev, Theodore Ts'o <tytso@mit.edu>,
"Darrick J. Wong" <djwong@kernel.org>,
Andrey Albershteyn <aalbersh@redhat.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
David Sterba <dsterba@suse.com>,
linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [GIT PULL] fsverity updates for 7.0
Date: Thu, 12 Feb 2026 09:38:02 -0800 [thread overview]
Message-ID: <20260212173802.GA2269@sol> (raw)
In-Reply-To: <20260212101143.GA7951@lst.de>
On Thu, Feb 12, 2026 at 11:11:43AM +0100, Christoph Hellwig wrote:
> Note that this had a merge conflict in linux-next. So unless that
> went away, it needs a merge resolution like:
>
> https://lore.kernel.org/fsverity/20260203053604.GC15956@lst.de/T/#m291294c1f6b7368d3c426ee47e6d23dc854b3ba6
It will be needed after both this pull request and the f2fs pull request
are merged. Currently, the f2fs pull request hasn't been sent yet.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-02-12 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 1:26 [GIT PULL] fsverity updates for 7.0 Eric Biggers
2026-02-12 1:26 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-02-12 10:11 ` Christoph Hellwig
2026-02-12 10:11 ` [f2fs-dev] " Christoph Hellwig
2026-02-12 17:38 ` Eric Biggers [this message]
2026-02-12 17:38 ` Eric Biggers via Linux-f2fs-devel
2026-02-12 19:13 ` pr-tracker-bot
2026-02-12 19:13 ` pr-tracker-bot--- via Linux-f2fs-devel
2026-05-11 1:41 ` patchwork-bot+f2fs
2026-05-11 1:41 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=20260212173802.GA2269@sol \
--to=ebiggers@kernel.org \
--cc=aalbersh@redhat.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=fsverity@lists.linux.dev \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--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 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.