From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] fscrypt: remove filesystem specific build config option
Date: Thu, 24 Jan 2019 16:22:36 -0500 [thread overview]
Message-ID: <20190124212236.GF8785@mit.edu> (raw)
In-Reply-To: <20190124182949.GB10448@gmail.com>
On Thu, Jan 24, 2019 at 10:29:50AM -0800, Eric Biggers wrote:
>
> Hi Ted, that sounds good to me. I assume you know how to get that set up?
> Also, should I go ahead and send a patch that adds myself to the MAINTAINERS
> file?
I have the request to the git.kernel.org folks and the edits to the
MAINTAINERS file already done, so I'll send them out shortly. :-)
- Ted
prev parent reply other threads:[~2019-01-24 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 23:32 [PATCH] fscrypt: remove filesystem specific build config option Guenter Roeck
2019-01-11 1:01 ` [f2fs-dev] " Eric Biggers
2019-01-24 5:03 ` Theodore Y. Ts'o
2019-01-24 18:29 ` Eric Biggers
2019-01-24 21:22 ` Theodore Y. Ts'o [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=20190124212236.GF8785@mit.edu \
--to=tytso@mit.edu \
--cc=chandan@linux.vnet.ibm.com \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).