From: patchwork-bot+f2fs@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: fsverity@lists.linux.dev, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/2] fsverity: simplify initcall and move sysctl registration
Date: Mon, 04 Sep 2023 18:11:09 +0000 [thread overview]
Message-ID: <169385106912.19669.17692351155547248889.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230705212743.42180-1-ebiggers@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Eric Biggers <ebiggers@google.com>:
On Wed, 5 Jul 2023 14:27:41 -0700 you wrote:
> This series simplifies handling of errors during the fsverity_init()
> initcall, and moves the sysctl registration out of signature.c so that
> it is not unnecessarily tied to the builtin signature feature.
>
> Eric Biggers (2):
> fsverity: simplify handling of errors during initcall
> fsverity: move sysctl registration out of signature.c
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] fsverity: simplify handling of errors during initcall
https://git.kernel.org/jaegeuk/f2fs/c/e77000ccc531
- [f2fs-dev,2/2] fsverity: move sysctl registration out of signature.c
https://git.kernel.org/jaegeuk/f2fs/c/456ae5fe9b44
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-09-04 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 21:27 [f2fs-dev] [PATCH 0/2] fsverity: simplify initcall and move sysctl registration Eric Biggers
2023-07-05 21:27 ` [f2fs-dev] [PATCH 1/2] fsverity: simplify handling of errors during initcall Eric Biggers
2023-07-05 21:27 ` [f2fs-dev] [PATCH 2/2] fsverity: move sysctl registration out of signature.c Eric Biggers
[not found] ` <CGME20230906134906eucas1p18f20ec4bd1aa89ce9c8c6495255d442f@eucas1p1.samsung.com>
[not found] ` <20230906134904.4zbqdldrq2k4rqfn@localhost>
2023-09-07 4:12 ` Eric Biggers
2023-09-04 18:11 ` 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=169385106912.19669.17692351155547248889.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).