public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	David Howells <dhowells@redhat.com>
Subject: [GIT PULL] fscrypt updates for 6.15
Date: Sun, 23 Mar 2025 15:19:23 -0700	[thread overview]
Message-ID: <20250323221923.GA9584@sol.localdomain> (raw)

The following changes since commit 0ad2507d5d93f39619fc42372c347d6006b64319:

  Linux 6.14-rc3 (2025-02-16 14:02:44 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/fscrypt/linux.git tags/fscrypt-for-linus

for you to fetch changes up to 13dc8eb90067f3aae45269214978e552400d5e28:

  fscrypt: mention init_on_free instead of page poisoning (2025-03-04 13:02:45 -0800)

----------------------------------------------------------------

A fix for an issue where CONFIG_FS_ENCRYPTION could be enabled without
some of its dependencies, and a small documentation update.

----------------------------------------------------------------
Eric Biggers (3):
      Revert "fscrypt: relax Kconfig dependencies for crypto API algorithms"
      fscrypt: drop obsolete recommendation to enable optimized ChaCha20
      fscrypt: mention init_on_free instead of page poisoning

 Documentation/filesystems/fscrypt.rst |  8 ++------
 fs/crypto/Kconfig                     | 20 ++++++++------------
 2 files changed, 10 insertions(+), 18 deletions(-)

             reply	other threads:[~2025-03-23 22:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-23 22:19 Eric Biggers [this message]
2025-03-26  2:05 ` [GIT PULL] fscrypt updates for 6.15 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=20250323221923.GA9584@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=ardb@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --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