From: patchwork-bot+f2fs@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: torvalds@linux-foundation.org, fsverity@lists.linux.dev,
tytso@mit.edu, djwong@kernel.org, aalbersh@redhat.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, dsterba@suse.com,
linux-fsdevel@vger.kernel.org, jack@suse.cz,
linux-ext4@vger.kernel.org, hch@lst.de,
linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [GIT PULL] fsverity updates for 7.0
Date: Mon, 11 May 2026 01:41:12 +0000 [thread overview]
Message-ID: <177846367229.1975880.775776220391157336.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260212012652.GA8885@sol>
Hello:
This pull request was applied to jaegeuk/f2fs.git (dev)
by Linus Torvalds <torvalds@linux-foundation.org>:
On Wed, 11 Feb 2026 17:26:52 -0800 you wrote:
> The following changes since commit 63804fed149a6750ffd28610c5c1c98cce6bd377:
>
> Linux 6.19-rc7 (2026-01-25 14:11:24 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/fs/fsverity/linux.git tags/fsverity-for-linus
>
> [...]
Here is the summary with links:
- [f2fs-dev,GIT,PULL] fsverity updates for 7.0
https://git.kernel.org/jaegeuk/f2fs/c/1bfaee9d3351
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-11 1:42 UTC|newest]
Thread overview: 5+ 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 10:11 ` Christoph Hellwig
2026-02-12 17:38 ` Eric Biggers
2026-02-12 19:13 ` [f2fs-dev] " pr-tracker-bot
2026-05-11 1:41 ` patchwork-bot+f2fs [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=177846367229.1975880.775776220391157336.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=aalbersh@redhat.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox