From: Heiko Carstens <hca@linux.ibm.com>
To: Juerg Haefliger <juerg.haefliger@canonical.com>
Cc: 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,
Juerg Haefliger <juergh@canonical.com>
Subject: Re: [PATCH 0/2] s390: Kconfig: Style cleanups
Date: Mon, 23 May 2022 11:39:31 +0200 [thread overview]
Message-ID: <YotWU/E8z2fJaqj7@osiris> (raw)
In-Reply-To: <20220520115708.147841-1-juergh@canonical.com>
On Fri, May 20, 2022 at 01:57:06PM +0200, Juerg Haefliger wrote:
> The majority of the Kconfig files use a single tab for basic indentation
> and a single tab followed by two whitespaces for help text indentation.
> Fix the lines that don't follow this convention.
>
> While at it:
> - Add trailing comments to endif/endmenu statements for better
> readability.
>
> Juerg Haefliger (2):
> s390: Kconfig: Fix indentation and add comments
> s390: Kconfig.debug: Fix indentation
>
> arch/s390/Kconfig | 20 ++++++++++----------
> arch/s390/Kconfig.debug | 12 ++++++------
> 2 files changed, 16 insertions(+), 16 deletions(-)
Both applied (v2 for the first patch). Thanks!
next prev parent reply other threads:[~2022-05-23 9:39 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
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 ` Heiko Carstens [this message]
2022-05-25 9:39 ` [PATCH 0/2] s390: Kconfig: Style cleanups 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=YotWU/E8z2fJaqj7@osiris \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=juerg.haefliger@canonical.com \
--cc=juergh@canonical.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