From: Ingo Molnar <mingo@kernel.org>
To: Juerg Haefliger <juerg.haefliger@canonical.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] x86: Kconfig: Style cleanups
Date: Wed, 25 May 2022 15:38:35 +0200 [thread overview]
Message-ID: <Yo4xW+2u9obEt6Ay@gmail.com> (raw)
In-Reply-To: <20220525133203.52463-1-juerg.haefliger@canonical.com>
* Juerg Haefliger <juerg.haefliger@canonical.com> 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 missing trailing endif comments.
>
> Juerg Haefliger (2):
> x86: Kconfig: Fix indentation and add endif comments
> x86: Kconfig.debug: Fix indentation
>
> arch/x86/Kconfig | 101 ++++++++++++++++++++---------------------
> arch/x86/Kconfig.debug | 29 ++++++------
> 2 files changed, 63 insertions(+), 67 deletions(-)
Merged into tip:x86/cleanups, thanks Juerg!
Ingo
prev parent reply other threads:[~2022-05-25 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 13:32 [PATCH 0/2] x86: Kconfig: Style cleanups Juerg Haefliger
2022-05-25 13:32 ` [PATCH 1/2] x86: Kconfig: Fix indentation and add endif comments Juerg Haefliger
2022-05-25 13:43 ` [tip: x86/cleanups] x86/Kconfig: Fix indentation and add endif comments to arch/x86/Kconfig tip-bot2 for Juerg Haefliger
2022-05-25 13:32 ` [PATCH 2/2] x86: Kconfig.debug: Fix indentation Juerg Haefliger
2022-05-25 13:43 ` [tip: x86/cleanups] x86/Kconfig: Fix indentation of arch/x86/Kconfig.debug tip-bot2 for Juerg Haefliger
2022-05-25 13:38 ` Ingo Molnar [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=Yo4xW+2u9obEt6Ay@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=juerg.haefliger@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox