All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, carlos.bilbao@amd.com,
	elena.reshetova@intel.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH docs] MAINTAINERS: use tabs for indent of CONFIDENTIAL COMPUTING THREAT MODEL
Date: Wed,  3 Jan 2024 08:09:38 -0800	[thread overview]
Message-ID: <20240103160938.1006517-1-kuba@kernel.org> (raw)

There are two MAINTAINERS entries which snuck in during the previous
merge window which use spaces instead of tabs for indent. The rest
of the file uses tabs. Fix CONFIDENTIAL COMPUTING THREAT MODEL FOR
X86 VIRTUALIZATION (SNP/TDX).

Given the prevalence of using tabs some scripts (AKA my scripts)
assume tabs when parsing.

The faulty entry was added in commit 1f597b1a6ec2 ("docs: security:
Confidential computing intro and threat model for x86 virtualization")

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
 MAINTAINERS | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 6a9876df20f8..1ce437992a4d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5313,10 +5313,10 @@ W:	http://accessrunner.sourceforge.net/
 F:	drivers/usb/atm/cxacru.c
 
 CONFIDENTIAL COMPUTING THREAT MODEL FOR X86 VIRTUALIZATION (SNP/TDX)
-M:    Elena Reshetova <elena.reshetova@intel.com>
-M:    Carlos Bilbao <carlos.bilbao@amd.com>
-S:    Maintained
-F:    Documentation/security/snp-tdx-threat-model.rst
+M:	Elena Reshetova <elena.reshetova@intel.com>
+M:	Carlos Bilbao <carlos.bilbao@amd.com>
+S:	Maintained
+F:	Documentation/security/snp-tdx-threat-model.rst
 
 CONFIGFS
 M:	Joel Becker <jlbec@evilplan.org>
-- 
2.43.0


             reply	other threads:[~2024-01-03 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 16:09 Jakub Kicinski [this message]
2024-01-08 15:52 ` [PATCH docs] MAINTAINERS: use tabs for indent of CONFIDENTIAL COMPUTING THREAT MODEL Carlos Bilbao
2024-01-08 18:39 ` Jonathan Corbet

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=20240103160938.1006517-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=carlos.bilbao@amd.com \
    --cc=corbet@lwn.net \
    --cc=elena.reshetova@intel.com \
    --cc=linux-doc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.