Linux-FSCrypt Archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Dongsoo Lee <letrhee@nsr.re.kr>
Subject: [PATCH 0/2] fscrypt: update the encryption mode docs
Date: Thu, 29 Jun 2023 23:48:09 -0700	[thread overview]
Message-ID: <20230630064811.22569-1-ebiggers@kernel.org> (raw)

This series improves the documentation for the encryption modes
supported by fscrypt.

Eric Biggers (2):
  fscrypt: improve the "Encryption modes and usage" section
  fscrypt: document the LEA support

 Documentation/filesystems/fscrypt.rst | 166 +++++++++++++++++++-------
 1 file changed, 121 insertions(+), 45 deletions(-)


base-commit: 82a2a51055895f419a3aaba15ffad419063191f0
-- 
2.41.0


             reply	other threads:[~2023-06-30  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  6:48 Eric Biggers [this message]
2023-06-30  6:48 ` [PATCH 1/2] fscrypt: improve the "Encryption modes and usage" section Eric Biggers
2023-06-30  6:48 ` [PATCH 2/2] fscrypt: document the LEA support Eric Biggers

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=20230630064811.22569-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=letrhee@nsr.re.kr \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).