From: Tony Lindgren <tony@atomide.com>
To: Juerg Haefliger <juerg.haefliger@canonical.com>
Cc: arnd@arndb.de, juergh@canonical.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
olof@lixom.net, sfr@canb.auug.org.au
Subject: Re: [PATCH v2] ARM: omap1: Kconfig: Fix indentation
Date: Mon, 27 Mar 2023 09:55:18 +0300 [thread overview]
Message-ID: <20230327065518.GQ7501@atomide.com> (raw)
In-Reply-To: <20230315091152.132443-1-juerg.haefliger@canonical.com>
* Juerg Haefliger <juerg.haefliger@canonical.com> [230315 11:12]:
> 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>
>
> ---
> v2: Updated for latest upstream.
Thans for updating it, applying into omap-for-v6.4/omap1.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Juerg Haefliger <juerg.haefliger@canonical.com>
Cc: arnd@arndb.de, juergh@canonical.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
olof@lixom.net, sfr@canb.auug.org.au
Subject: Re: [PATCH v2] ARM: omap1: Kconfig: Fix indentation
Date: Mon, 27 Mar 2023 09:55:18 +0300 [thread overview]
Message-ID: <20230327065518.GQ7501@atomide.com> (raw)
In-Reply-To: <20230315091152.132443-1-juerg.haefliger@canonical.com>
* Juerg Haefliger <juerg.haefliger@canonical.com> [230315 11:12]:
> 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>
>
> ---
> v2: Updated for latest upstream.
Thans for updating it, applying into omap-for-v6.4/omap1.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-27 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 22:50 linux-next: manual merge of the omap tree with the arm-soc tree Stephen Rothwell
2023-01-09 22:50 ` Stephen Rothwell
2023-01-19 10:11 ` Tony Lindgren
2023-01-19 10:11 ` Tony Lindgren
2023-03-15 9:11 ` [PATCH v2] ARM: omap1: Kconfig: Fix indentation Juerg Haefliger
2023-03-15 9:11 ` Juerg Haefliger
2023-03-27 6:55 ` Tony Lindgren [this message]
2023-03-27 6:55 ` Tony Lindgren
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=20230327065518.GQ7501@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=juerg.haefliger@canonical.com \
--cc=juergh@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.