linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] ext4 crypto: migrate into vfs's crypto engine
Date: Thu, 14 Jul 2016 19:53:30 -0700	[thread overview]
Message-ID: <20160715025330.GA44979@jaegeuk> (raw)
In-Reply-To: <20160715024526.GA26465@thunk.org>

On Thu, Jul 14, 2016 at 10:45:26PM -0400, Theodore Ts'o wrote:
> On Sat, May 07, 2016 at 11:52:50AM -0700, Jaegeuk Kim wrote:
> > 
> > From 593e56e680f962c5e9cc57afa19bda4c654bd841 Mon Sep 17 00:00:00 2001
> > From: Jaegeuk Kim <jaegeuk@kernel.org>
> > Date: Wed, 10 Feb 2016 16:26:25 -0800
> > Subject: [PATCH] ext4 crypto: migrate into vfs's crypto engine
> > 
> > This patch removes the most parts of internal crypto codes.
> > And then, it modifies and adds some ext4-specific crypt codes to use the generic
> > facility.
> > 
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> 
> I've added this patch to the ext4.git tree.  I will also include the
> following MAINTAINERS file update.

Got it, thank you.

> 
> Thanks,
> 
> 							- Ted
> 							
> commit 598c7d7abc832e35677b851f6afb93141c09993b
> Author: Theodore Ts'o <tytso@mit.edu>
> Date:   Thu Jul 14 22:44:13 2016 -0400
> 
>     MAINTAINRES: fs-crypto maintainers update
>     
>     Signed-off-by: Theodore Ts'o <tytso@mit.edu>
>     Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7304d2e..b2234f8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4925,6 +4925,13 @@ F:	Documentation/filesystems/caching/
>  F:	fs/fscache/
>  F:	include/linux/fscache*.h
>  
> +FS-CRYPTO: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
> +M:	Theodore Y. Ts'o <tytso@mit.edu>
> +M:	Jaegeuk Kim <jaegeuk@kernel.org>
> +S:	Supported
> +F:	fs/crypto/
> +F:	include/linux/fscrypto.h
> +
>  F2FS FILE SYSTEM
>  M:	Jaegeuk Kim <jaegeuk@kernel.org>
>  M:	Changman Lee <cm224.lee@samsung.com>

      reply	other threads:[~2016-07-15  2:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26  0:15 [PATCH] ext4 crypto: migrate into vfs's crypto engine Jaegeuk Kim
2016-05-05  3:20 ` Theodore Ts'o
2016-05-05  4:22   ` Jaegeuk Kim
2016-05-05 12:44     ` Theodore Ts'o
2016-05-06  0:25       ` Jaegeuk Kim
2016-05-07  2:31 ` Eric Biggers
2016-05-07 18:46   ` Jaegeuk Kim
2016-05-07 18:52 ` [PATCH v2] " Jaegeuk Kim
2016-07-15  2:45   ` Theodore Ts'o
2016-07-15  2:53     ` Jaegeuk Kim [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=20160715025330.GA44979@jaegeuk \
    --to=jaegeuk@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).