From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Micah Morton <mortonm@chromium.org>
Cc: Joe Perches <joe@perches.com>,
linux-security-module@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH RESEND] MAINTAINERS: fix style in SAFESETID SECURITY MODULE
Date: Thu, 16 Jan 2020 19:58:44 +0100 [thread overview]
Message-ID: <20200116185844.11201-1-lukas.bulwahn@gmail.com> (raw)
Commit fc5b34a35458 ("Add entry in MAINTAINERS file for SafeSetID LSM")
slips in some formatting with spaces instead of tabs, which
./scripts/checkpatch.pl -f MAINTAINERS complains about:
WARNING: MAINTAINERS entries use one tab after TYPE:
#14394: FILE: MAINTAINERS:14394:
+M: Micah Morton <mortonm@chromium.org>
WARNING: MAINTAINERS entries use one tab after TYPE:
#14395: FILE: MAINTAINERS:14395:
+S: Supported
WARNING: MAINTAINERS entries use one tab after TYPE:
#14396: FILE: MAINTAINERS:14396:
+F: security/safesetid/
WARNING: MAINTAINERS entries use one tab after TYPE:
#14397: FILE: MAINTAINERS:14397:
+F: Documentation/admin-guide/LSM/SafeSetID.rst
Fixes: fc5b34a35458 ("Add entry in MAINTAINERS file for SafeSetID LSM")
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
applies cleanly on v5.5-rc6 and next-20200116
Micah, please pick this patch.
MAINTAINERS | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a66cb722c675..d2aa9db61ab6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14415,10 +14415,10 @@ F: drivers/media/pci/saa7146/
F: include/media/drv-intf/saa7146*
SAFESETID SECURITY MODULE
-M: Micah Morton <mortonm@chromium.org>
-S: Supported
-F: security/safesetid/
-F: Documentation/admin-guide/LSM/SafeSetID.rst
+M: Micah Morton <mortonm@chromium.org>
+S: Supported
+F: security/safesetid/
+F: Documentation/admin-guide/LSM/SafeSetID.rst
SAMSUNG AUDIO (ASoC) DRIVERS
M: Krzysztof Kozlowski <krzk@kernel.org>
--
2.17.1
reply other threads:[~2020-01-16 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200116185844.11201-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mortonm@chromium.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).