From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Wed, 30 Dec 2020 15:40:11 +0000 (+0100)
Subject: comment cleaned up in 5.4 patch
X-Git-Tag: v4.19.165~45
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=7739eff515921d42d05c21b7724a9de9f1bb174a;p=thirdparty%2Fkernel%2Fstable-queue.git

comment cleaned up in 5.4 patch
---

diff --git a/queue-5.4/fscrypt-remove-kernel-internal-constants-from-uapi-header.patch b/queue-5.4/fscrypt-remove-kernel-internal-constants-from-uapi-header.patch
index 6bd7afa4984..b97f7c36af5 100644
--- a/queue-5.4/fscrypt-remove-kernel-internal-constants-from-uapi-header.patch
+++ b/queue-5.4/fscrypt-remove-kernel-internal-constants-from-uapi-header.patch
@@ -9,7 +9,6 @@ Message-ID: <20201228184747.56259-1-ebiggers@kernel.org>
 From: Eric Biggers <ebiggers@google.com>
 
 commit 3ceb6543e9cf6ed87cc1fbc6f23ca2db903564cd upstream.
-[Please apply to 5.4-stable.]
 
 There isn't really any valid reason to use __FSCRYPT_MODE_MAX or
 FSCRYPT_POLICY_FLAGS_VALID in a userspace program.  These constants are