From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-doc@vger.kernel.org, linux-mips@linux-mips.org,
linux-s390@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-fsdevel@vger.kernel.org, adilger.kernel@dilger.ca,
ebiggers@kernel.org, jaegeuk@kernel.org, yuchao0@huawei.com,
corbet@lwn.net, ralf@linux-mips.org, paul.burton@mips.com,
jhogan@kernel.org, green.hu@gmail.com, deanbo422@gmail.com,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
richard@nod.at, dedekind1@gmail.com, adrian.hunter@intel.com,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH V3 0/9] Remove fs specific fscrypt and fsverity build config options
Date: Mon, 10 Dec 2018 01:06:10 -0500 [thread overview]
Message-ID: <20181210060610.GJ1840@mit.edu> (raw)
In-Reply-To: <20181208065144.19486-1-chandan@linux.vnet.ibm.com>
Chandan,
Thanks! I've applied this patch series to the fscrypt git tree.
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: linux-mips@linux-mips.org, linux-doc@vger.kernel.org,
jhogan@kernel.org, yuchao0@huawei.com, heiko.carstens@de.ibm.com,
linux-mtd@lists.infradead.org, deanbo422@gmail.com,
linux-s390@vger.kernel.org, corbet@lwn.net, richard@nod.at,
ebiggers@kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, green.hu@gmail.com,
jaegeuk@kernel.org, dedekind1@gmail.com, adrian.hunter@intel.com,
ralf@linux-mips.org, linux-f2fs-devel@lists.sourceforge.net,
paul.burton@mips.com, schwidefsky@de.ibm.com,
adilger.kernel@dilger.ca, viro@zeniv.linux.org.uk
Subject: Re: [PATCH V3 0/9] Remove fs specific fscrypt and fsverity build config options
Date: Mon, 10 Dec 2018 01:06:10 -0500 [thread overview]
Message-ID: <20181210060610.GJ1840@mit.edu> (raw)
In-Reply-To: <20181208065144.19486-1-chandan@linux.vnet.ibm.com>
Chandan,
Thanks! I've applied this patch series to the fscrypt git tree.
- Ted
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2018-12-10 6:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 6:51 [PATCH V3 0/9] Remove fs specific fscrypt and fsverity build config options Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-08 6:51 ` [PATCH V3 1/9] ext4: use IS_ENCRYPTED() to check encryption status Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-08 6:51 ` [PATCH V3 2/9] f2fs: " Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-10 18:06 ` Eric Biggers
2018-12-10 18:06 ` Eric Biggers
2018-12-08 6:51 ` [PATCH V3 3/9] fscrypt: remove filesystem specific build config option Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-10 18:13 ` Eric Biggers
2018-12-10 18:13 ` Eric Biggers
2018-12-08 6:51 ` [PATCH V3 4/9] Add S_VERITY and IS_VERITY() Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-08 6:51 ` [PATCH V3 5/9] ext4: use IS_VERITY() to check inode's fsverity status Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-08 6:51 ` [PATCH V3 6/9] f2fs: " Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-10 18:17 ` Eric Biggers
2018-12-10 18:17 ` Eric Biggers
2018-12-08 6:51 ` [PATCH V3 7/9] fsverity: Remove filesystem specific build config option Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-10 18:19 ` Eric Biggers
2018-12-10 18:19 ` Eric Biggers
2018-12-08 6:51 ` [PATCH V3 8/9] fsverity: Move verity status check to fsverity_file_open Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-10 17:26 ` Eric Biggers
2018-12-10 17:26 ` Eric Biggers
2018-12-08 6:51 ` [PATCH V3 9/9] fsverity: Move verity status check to fsverity_prepare_setattr Chandan Rajendra
2018-12-08 6:51 ` Chandan Rajendra
2018-12-10 6:06 ` Theodore Y. Ts'o [this message]
2018-12-10 6:06 ` [PATCH V3 0/9] Remove fs specific fscrypt and fsverity build config options Theodore Y. Ts'o
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=20181210060610.GJ1840@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=adrian.hunter@intel.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=deanbo422@gmail.com \
--cc=dedekind1@gmail.com \
--cc=ebiggers@kernel.org \
--cc=green.hu@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jaegeuk@kernel.org \
--cc=jhogan@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=richard@nod.at \
--cc=schwidefsky@de.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuchao0@huawei.com \
/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.