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 6bd7afa49841c0001094874deae4153109812ff9..b97f7c36af54e5b2b825859083fb6eba1ce27ce6 100644 (file)
--- 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