[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d86b87edc9c9fa33b6a18fac8b160ee56e6a07c.camel@perches.com>
Date: Fri, 20 May 2022 10:15:38 -0700
From: Joe Perches <joe@...ches.com>
To: Juerg Haefliger <juerg.haefliger@...onical.com>, hca@...ux.ibm.com,
gor@...ux.ibm.com, agordeev@...ux.ibm.com,
borntraeger@...ux.ibm.com, svens@...ux.ibm.com,
linux-s390@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Juerg Haefliger <juergh@...onical.com>
Subject: Re: [PATCH 1/2] s390: Kconfig: Fix indentation and add comments
On Fri, 2022-05-20 at 13:57 +0200, Juerg Haefliger wrote:
> The convention for indentation seems to be a single tab. Help text is
> further indented by an additional two whitespaces. Fix the lines that
> violate these rules.
>
> While add it, add trailing comments to endmenu statements for better
> readability.
[]
> diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
[]
> @@ -607,7 +607,7 @@ config RANDOMIZE_BASE
> as a security feature that deters exploit attempts relying on
> knowledge of the location of kernel internals.
>
> -endmenu
> +endmenu # "Processor type and features"
An endmenu comment is relatively unusual.
$ git grep '^endmenu' -- '*/Kconfig*' | wc -l
394
$ git grep '^endmenu.*#' -- '*/Kconfig*' | wc -l
20
I believe it doesn't really help readability.
Powered by blists - more mailing lists