From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] vfs ecryptfs mount api
Date: Tue, 26 Nov 2024 12:26:04 +0100 [thread overview]
Message-ID: <20241126-vfs-ecryptfs-f20bc3c7b06e@brauner> (raw)
Hey Linus,
/* Summary */
This contains the work to convert ecryptfs to the new mount api.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-6)
Debian clang version 16.0.6 (27+b1)
All patches have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit b4201b51d93eac77f772298a96bfedbdb0c7150c:
Merge patch series "Convert ecryptfs to use folios" (2024-11-05 17:20:17 +0100)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.13.ecryptfs.mount.api
for you to fetch changes up to 7ff3e945a35ac472c6783403eae1e7519d96f1cf:
ecryptfs: Fix spelling mistake "validationg" -> "validating" (2024-11-15 11:51:29 +0100)
----------------------------------------------------------------
vfs-6.13.ecryptfs.mount.api
----------------------------------------------------------------
Christian Brauner (1):
Merge patch series "ecryptfs: convert to the new mount API"
Colin Ian King (1):
ecryptfs: Fix spelling mistake "validationg" -> "validating"
Eric Sandeen (2):
ecryptfs: Factor out mount option validation
ecryptfs: Convert ecryptfs to use the new mount API
fs/ecryptfs/main.c | 401 +++++++++++++++++++++++++++--------------------------
1 file changed, 205 insertions(+), 196 deletions(-)
next reply other threads:[~2024-11-26 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 11:26 Christian Brauner [this message]
2024-11-26 21:42 ` 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=20241126-vfs-ecryptfs-f20bc3c7b06e@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®