From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Juerg Haefliger <juerg.haefliger@canonical.com>,
ysato@users.sourceforge.jp, dalias@libc.org,
linux-sh@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] sh/mm: Kconfig: Fix indentation
Date: Thu, 26 May 2022 11:13:47 +0300 [thread overview]
Message-ID: <be49dcae-af31-c825-6ab4-05c59deec9d8@gmail.com> (raw)
In-Reply-To: <20220525124007.45328-5-juerg.haefliger@canonical.com>
On 5/25/22 3:40 PM, 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
s/whitespaces/spaces/. And you don't touch the help text here...
> violate these rules.
>
> Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com>
[...]
MBR, Sergey
next prev parent reply other threads:[~2022-05-26 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 12:40 [PATCH 0/4] sh: Kconfig: Style cleanups Juerg Haefliger
2022-05-25 12:40 ` [PATCH 1/4] sh: Kconfig: Fix indentation Juerg Haefliger
2022-05-26 8:21 ` Sergei Shtylyov
2022-05-27 12:02 ` [PATCH 1/4 v2] sh: Kconfig: Fix indentation and remove trailing whitespaces Juerg Haefliger
2022-05-25 12:40 ` [PATCH 2/4] sh: Kconfig.cpu: Fix indentation Juerg Haefliger
2022-05-25 16:14 ` Sergei Shtylyov
2022-05-25 18:31 ` [PATCH 2/4 v2] sh: Kconfig.cpu: Remove trailing whitespace Juerg Haefliger
2022-05-25 12:40 ` [PATCH 3/4] sh/boards: Kconfig: Fix indentation Juerg Haefliger
2022-05-25 18:34 ` Sergei Shtylyov
2022-05-27 12:04 ` [PATCH 3/4 v2] sh/boards: Kconfig: Fix indentation and remove trailing whitespaces Juerg Haefliger
2022-05-25 12:40 ` [PATCH 4/4] sh/mm: Kconfig: Fix indentation Juerg Haefliger
2022-05-26 8:13 ` Sergei Shtylyov [this message]
2022-05-27 12:05 ` [PATCH 4/4 v2] " 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=be49dcae-af31-c825-6ab4-05c59deec9d8@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=dalias@libc.org \
--cc=juerg.haefliger@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®