From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Guenter Roeck <groeck@google.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Doug Anderson <dianders@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>, Chao Yu <chao@kernel.org>,
Ryo Hashimoto <hashimoto@chromium.org>,
Vadim Sukhomlinov <sukhomlinov@google.com>,
Guenter Roeck <groeck@chromium.org>,
Andrey Pronin <apronin@chromium.org>,
linux-doc@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jonathan Corbet <corbet@lwn.net>,
LKML <linux-kernel@vger.kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-fscrypt@vger.kernel.org,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] Revert "ext4 crypto: fix to check feature status before get policy"
Date: Sun, 3 Nov 2019 08:19:44 -0500 [thread overview]
Message-ID: <20191103131944.GB20210@mit.edu> (raw)
In-Reply-To: <CABXOdTeu3KdT=arT+AKAOiPPM0U45krUfmDx6NH5nmDZ0pPa=A@mail.gmail.com>
On Sat, Nov 02, 2019 at 03:10:17PM -0700, Guenter Roeck wrote:
>
> This change is now in our code base:
>
> https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/5c5b06fded399013b9cce3d504c3d968ee84ab8b
>
> If the revert has not made it upstream, I would suggest to hold it off
> for the time being. I'll do more testing next week, but as it looks
> like it may no longer be needed, at least not from a Chrome OS
> perspective.
Thanks, I'll hold off on requesting a pull request from Linus for this
change.
- Ted
next prev parent reply other threads:[~2019-11-03 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 17:06 [PATCH] Revert "ext4 crypto: fix to check feature status before get policy" Douglas Anderson
2019-10-30 17:37 ` Eric Biggers
2019-10-30 17:51 ` Doug Anderson
2019-10-30 19:02 ` Eric Biggers
2019-10-30 20:57 ` Eric Biggers
2019-10-30 21:59 ` Doug Anderson
2019-10-31 17:52 ` Doug Anderson
2019-11-01 4:36 ` Eric Biggers
2019-11-01 13:32 ` Guenter Roeck
2019-11-01 18:17 ` Guenter Roeck
2019-11-02 22:10 ` Guenter Roeck
2019-11-03 13:19 ` Theodore Y. Ts'o [this message]
2019-11-04 7:45 ` Chao Yu
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=20191103131944.GB20210@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=apronin@chromium.org \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=dianders@chromium.org \
--cc=ebiggers@kernel.org \
--cc=groeck@chromium.org \
--cc=groeck@google.com \
--cc=gwendal@chromium.org \
--cc=hashimoto@chromium.org \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sukhomlinov@google.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 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).