From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Daniel Rosenberg <drosen@google.com>,
Eric Biggers <ebiggers@kernel.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Chao Yu <chao@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Richard Weinberger <richard@nod.at>,
linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mtd@lists.infradead.org,
Gabriel Krisman Bertazi <krisman@collabora.com>,
kernel-team@android.com
Subject: Re: [PATCH v2 2/3] fscrypt: Have filesystems handle their d_ops
Date: Tue, 17 Nov 2020 12:34:47 -0500 [thread overview]
Message-ID: <20201117173447.GF445084@mit.edu> (raw)
In-Reply-To: <20201117170411.GC1636127@google.com>
On Tue, Nov 17, 2020 at 09:04:11AM -0800, Jaegeuk Kim wrote:
>
> I'd like to pick this patch series in f2fs/dev for -next, so please let me know
> if you have any concern.
No concern for me as far as ext4 is concerned, thanks!
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: kernel-team@android.com, Daniel Rosenberg <drosen@google.com>,
Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-ext4@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [f2fs-dev] [PATCH v2 2/3] fscrypt: Have filesystems handle their d_ops
Date: Tue, 17 Nov 2020 12:34:47 -0500 [thread overview]
Message-ID: <20201117173447.GF445084@mit.edu> (raw)
In-Reply-To: <20201117170411.GC1636127@google.com>
On Tue, Nov 17, 2020 at 09:04:11AM -0800, Jaegeuk Kim wrote:
>
> I'd like to pick this patch series in f2fs/dev for -next, so please let me know
> if you have any concern.
No concern for me as far as ext4 is concerned, thanks!
- Ted
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: kernel-team@android.com, Daniel Rosenberg <drosen@google.com>,
Richard Weinberger <richard@nod.at>, Chao Yu <chao@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-ext4@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [PATCH v2 2/3] fscrypt: Have filesystems handle their d_ops
Date: Tue, 17 Nov 2020 12:34:47 -0500 [thread overview]
Message-ID: <20201117173447.GF445084@mit.edu> (raw)
In-Reply-To: <20201117170411.GC1636127@google.com>
On Tue, Nov 17, 2020 at 09:04:11AM -0800, Jaegeuk Kim wrote:
>
> I'd like to pick this patch series in f2fs/dev for -next, so please let me know
> if you have any concern.
No concern for me as far as ext4 is concerned, thanks!
- Ted
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-11-17 17:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 4:03 [PATCH v2 0/3] Add support for Encryption and Casefolding in F2FS Daniel Rosenberg
2020-11-17 4:03 ` Daniel Rosenberg
2020-11-17 4:03 ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2020-11-17 4:03 ` [PATCH v2 1/3] libfs: Add generic function for setting dentry_ops Daniel Rosenberg
2020-11-17 4:03 ` Daniel Rosenberg
2020-11-17 4:03 ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2020-11-17 17:33 ` Theodore Y. Ts'o
2020-11-17 17:33 ` Theodore Y. Ts'o
2020-11-17 17:33 ` [f2fs-dev] " Theodore Y. Ts'o
2020-11-17 18:16 ` Eric Biggers
2020-11-17 18:16 ` Eric Biggers
2020-11-17 18:16 ` [f2fs-dev] " Eric Biggers
2020-11-17 18:36 ` Eric Biggers
2020-11-17 18:36 ` Eric Biggers
2020-11-17 18:36 ` Eric Biggers
2020-11-17 4:03 ` [PATCH v2 2/3] fscrypt: Have filesystems handle their d_ops Daniel Rosenberg
2020-11-17 4:03 ` Daniel Rosenberg
2020-11-17 4:03 ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2020-11-17 14:03 ` Theodore Y. Ts'o
2020-11-17 14:03 ` Theodore Y. Ts'o
2020-11-17 14:03 ` [f2fs-dev] " Theodore Y. Ts'o
2020-11-17 17:04 ` Jaegeuk Kim
2020-11-17 17:04 ` Jaegeuk Kim
2020-11-17 17:04 ` [f2fs-dev] " Jaegeuk Kim
2020-11-17 17:34 ` Theodore Y. Ts'o [this message]
2020-11-17 17:34 ` Theodore Y. Ts'o
2020-11-17 17:34 ` [f2fs-dev] " Theodore Y. Ts'o
2020-11-17 18:31 ` Eric Biggers
2020-11-17 18:31 ` Eric Biggers
2020-11-17 18:31 ` [f2fs-dev] " Eric Biggers
2020-11-17 4:03 ` [PATCH v2 3/3] f2fs: Handle casefolding with Encryption Daniel Rosenberg
2020-11-17 4:03 ` Daniel Rosenberg
2020-11-17 4:03 ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2020-11-17 14:06 ` Dan Carpenter
2020-11-17 14:06 ` [kbuild] " Dan Carpenter
2020-11-17 18:50 ` Eric Biggers
2020-11-17 18:50 ` Eric Biggers
2020-11-17 18:50 ` [f2fs-dev] " Eric Biggers
2020-11-18 6:22 ` Daniel Rosenberg
2020-11-18 6:22 ` Daniel Rosenberg
2020-11-18 6:22 ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2020-11-18 6:27 ` Eric Biggers
2020-11-18 6:27 ` Eric Biggers
2020-11-18 6:27 ` [f2fs-dev] " Eric Biggers
2020-11-18 1:03 ` kernel test robot
2020-11-17 18:53 ` [PATCH v2 0/3] Add support for Encryption and Casefolding in F2FS Eric Biggers
2020-11-17 18:53 ` Eric Biggers
2020-11-17 18:53 ` [f2fs-dev] " 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=20201117173447.GF445084@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=chao@kernel.org \
--cc=drosen@google.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.