From: Theodore Ts'o <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Eric Biggers <ebiggers@google.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] fscrypto: require write access to mount to set encryption policy
Date: Sat, 10 Sep 2016 01:20:28 -0400 [thread overview]
Message-ID: <20160910052028.e5xnxysyhv4bjibn@thunk.org> (raw)
In-Reply-To: <20160910044049.GD34151@jaegeuk>
On Fri, Sep 09, 2016 at 09:40:49PM -0700, Jaegeuk Kim wrote:
> Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
Thanks for acking this so quickly! I'll send all three fixes to
Linus, then.
> It'd be better to fix the below basic warnings tho.
Thanks, I've fixed the line over 80 characters warning. The rest of
the file uses "printk(KERN_WARNING, ..." and that's a fairly pedantic
warning so I'm just going to ignore it.
- Ted
prev parent reply other threads:[~2016-09-10 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 21:20 [PATCH] fscrypto: require write access to mount to set encryption policy Eric Biggers
2016-09-10 4:15 ` Theodore Ts'o
2016-09-10 4:40 ` Jaegeuk Kim
2016-09-10 5:20 ` Theodore 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=20160910052028.e5xnxysyhv4bjibn@thunk.org \
--to=tytso@mit.edu \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@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 NNTP newsgroup(s).