From: Kees Cook <keescook@chromium.org>
To: Juerg Haefliger <juerg.haefliger@canonical.com>
Cc: akpm@linux-foundation.org, Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>, Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Marco Elver <elver@google.com>,
Dan Li <ashimida@linux.alibaba.com>,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arch/Kconfig: Fix indentation
Date: Thu, 2 Feb 2023 17:38:30 +0000 [thread overview]
Message-ID: <63dbf517.a70a0220.d9b66.9217@mx.google.com> (raw)
In-Reply-To: <20230201162435.218368-1-juerg.haefliger@canonical.com>
On Wed, Feb 01, 2023 at 05:24:35PM +0100, 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.
>
> Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
prev parent reply other threads:[~2023-02-02 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 14:10 [PATCH] ARM: Kconfig: Fix indentation and add comments Juerg Haefliger
2022-05-18 5:48 ` [PATCH v2] arch/Kconfig: " Juerg Haefliger
2023-02-01 16:24 ` [PATCH v3] arch/Kconfig: Fix indentation Juerg Haefliger
2023-02-02 17:38 ` 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=63dbf517.a70a0220.d9b66.9217@mx.google.com \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=ashimida@linux.alibaba.com \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=frederic@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=juerg.haefliger@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=trix@redhat.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
Powered by JetHome