From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Elena Reshetova <elena.reshetova@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: use tabs in CONFIDENTIAL COMPUTING THREAT MODEL section
Date: Mon, 8 Jan 2024 10:01:48 -0600 [thread overview]
Message-ID: <6bf7da8b-6a0b-4c0d-959e-329d7cbd8cea@amd.com> (raw)
In-Reply-To: <20240108140852.20533-1-lukas.bulwahn@gmail.com>
Hello,
On 1/8/24 08:08, Lukas Bulwahn wrote:
> Commit 1f597b1a6ec2 ("docs: security: Confidential computing intro and
> threat model for x86 virtualization") adds new documentation and a
> corresponding MAINTAINERS section. It however uses spaces instead of a
> single tab for all the entries in that MAINTAINERS section.
>
> Although, the get_maintainer.pl script handles spaces instead of tabs
> silently, the MAINTAINERS will quickly get into a messy state with
> different indentations throughout the file. So, the checkpatch.pl script
> complains when spaces instead of a single tab are used.
>
> Fix this recently added section using tabs instead of spaces.
>
> Fixes: 1f597b1a6ec2 ("docs: security: Confidential computing intro and threat model for x86 virtualization")
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Jakub has already addressed this issue with the patch "[PATCH docs]
MAINTAINERS: use tabs for indent of CONFIDENTIAL COMPUTING THREAT MODEL"
from 1/3/24. Also, I recommend refraining from using the 'Fixes' tag for
things of this nature. NACK.
> ---
> MAINTAINERS | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index fa67e2624723..c76884e40434 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5296,10 +5296,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>
Thanks,
Carlos
prev parent reply other threads:[~2024-01-08 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 14:08 Lukas Bulwahn
2024-01-08 16:01 ` Carlos Bilbao [this message]
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=6bf7da8b-6a0b-4c0d-959e-329d7cbd8cea@amd.com \
--to=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--cc=elena.reshetova@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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
all inboxes | Powered by JetHome®