From: Kees Cook <keescook@chromium.org>
To: Juerg Haefliger <juerg.haefliger@canonical.com>
Cc: masahiroy@kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, juergh@canonical.com
Subject: Re: [PATCH] init: Remove leading spaces in Kconfig
Date: Mon, 24 May 2021 12:15:42 -0700 [thread overview]
Message-ID: <202105241215.85B9E20@keescook> (raw)
In-Reply-To: <20210517095848.82033-1-juergh@canonical.com>
On Mon, May 17, 2021 at 11:58:48AM +0200, Juerg Haefliger wrote:
> Remove leading spaces before tabs in Kconfig file(s) by running the
> following command:
>
> $ find init -name 'Kconfig*' | xargs sed -r -i 's/^[ ]+\t/\t/'
>
> Signed-off-by: Juerg Haefliger <juergh@canonical.com>
I'm impressed this is the only one! :) (And it's been there a long
time.)
Reviewed-by: Kees Cook <keescook@chromium.org>
-Kees
> ---
> init/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index 1ea12c64e4c9..9f1cde503739 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -2149,7 +2149,7 @@ config MODULE_SRCVERSION_ALL
> help
> Modules which contain a MODULE_VERSION get an extra "srcversion"
> field inserted into their modinfo section, which contains a
> - sum of the source files which made it. This helps maintainers
> + sum of the source files which made it. This helps maintainers
> see exactly which source was used to build a module (since
> others sometimes change the module source without updating
> the version). With this option, such a "srcversion" field
> --
> 2.27.0
>
--
Kees Cook
prev parent reply other threads:[~2021-05-24 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 9:58 [PATCH] init: Remove leading spaces in Kconfig Juerg Haefliger
2021-05-24 19:15 ` Kees Cook [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=202105241215.85B9E20@keescook \
--to=keescook@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=juerg.haefliger@canonical.com \
--cc=juergh@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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;
as well as URLs for NNTP newsgroup(s).