From: Juerg Haefliger <juerg.haefliger@canonical.com>
To: Joe Perches <joe@perches.com>
Cc: Juerg Haefliger <juerg.haefliger@canonical.com>,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] s390: Kconfig: Fix indentation and add comments
Date: Sat, 21 May 2022 12:35:03 +0200 [thread overview]
Message-ID: <20220521123503.03da61da@smeagol> (raw)
In-Reply-To: <8d86b87edc9c9fa33b6a18fac8b160ee56e6a07c.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
On Fri, 20 May 2022 10:15:38 -0700
Joe Perches <joe@perches.com> wrote:
> 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.
Thanks for the review. Will send a v2 without that.
...Juerg
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-21 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 11:57 [PATCH 0/2] s390: Kconfig: Style cleanups Juerg Haefliger
2022-05-20 11:57 ` [PATCH 1/2] s390: Kconfig: Fix indentation and add comments Juerg Haefliger
2022-05-20 17:15 ` Joe Perches
2022-05-21 10:35 ` Juerg Haefliger [this message]
2022-05-23 5:57 ` [PATCH 1/2 v2] s390: Kconfig: Fix indentation Juerg Haefliger
2022-05-20 11:57 ` [PATCH 2/2] s390: Kconfig.debug: " Juerg Haefliger
2022-05-23 9:39 ` [PATCH 0/2] s390: Kconfig: Style cleanups Heiko Carstens
2022-05-25 9:39 ` Heiko Carstens
2022-05-25 12:01 ` [PATCH 1/2 v3] s390: Kconfig: Fix indentation Juerg Haefliger
2022-05-25 12:01 ` [PATCH 2/2 v2] s390: Kconfig.debug: " Juerg Haefliger
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=20220521123503.03da61da@smeagol \
--to=juerg.haefliger@canonical.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.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