public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juerg Haefliger <juerg.haefliger@canonical.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Juerg Haefliger <juerg.haefliger@canonical.com>,
	linux@armlinux.org.uk, alim.akhtar@samsung.com,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: s3c: Kconfig: Style cleanups
Date: Tue, 7 Jun 2022 08:59:11 +0200	[thread overview]
Message-ID: <20220607085911.4b0f7f10@smeagol> (raw)
In-Reply-To: <63eabd40-761e-3b4e-c1be-43a12516e1b0@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

On Mon, 6 Jun 2022 11:14:28 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:

> On 06/06/2022 11:13, Krzysztof Kozlowski wrote:
> > On Mon, 23 May 2022 08:42:49 +0200, Juerg Haefliger 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 comments to endif statements and replace
> >> tabs before comments with whitespaces (which seems to be more common).
> >>
> >> [...]  
> > 
> > Applied, thanks!
> > 
> > [1/3] ARM: s3c: Kconfig: Fix indentation
> >       https://git.kernel.org/krzk/linux/c/076702da7e8a2472f8ac86f1179ddcc5e90febae
> > [3/3] ARM: s3c: Kconfig.s3c64xx: Fix indentation
> >       (no commit info)  
> 
> ...And dropped. This does not pass checkpatch. Please be sure you run
> scripts/checkpatch on your contributions.

I did and the check passed but email aliases don't work well in this scenario.
Will fix and resubmit.

...Juerg


> WARNING: From:/Signed-off-by: email address mismatch: 'From: Juerg
> Haefliger <juerg.haefliger@canonical.com>' != 'Signed-off-by: Juerg
> Haefliger <juergh@canonical.com>'
> 
> 
> Best regards,
> Krzysztof


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-06-07  6:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  6:42 [PATCH 0/3] ARM: s3c: Kconfig: Style cleanups Juerg Haefliger
2022-05-23  6:42 ` [PATCH 1/3] ARM: s3c: Kconfig: Fix indentation Juerg Haefliger
2022-05-23  6:42 ` [PATCH 2/3] ARM: s3c: Kconfig.s3c24xx: Fix indentation and replace some tabs Juerg Haefliger
2022-05-23  6:58   ` Alim Akhtar
2022-05-23  6:42 ` [PATCH 3/3] ARM: s3c: Kconfig.s3c64xx: Fix indentation Juerg Haefliger
2022-06-06  9:13 ` [PATCH 0/3] ARM: s3c: Kconfig: Style cleanups Krzysztof Kozlowski
2022-06-06  9:14   ` Krzysztof Kozlowski
2022-06-07  6:59     ` Juerg Haefliger [this message]
2022-06-09  8:21     ` [PATCH 0/3 v3] " Juerg Haefliger
2022-06-09  8:21       ` [PATCH 1/3 v3] ARM: s3c: Kconfig: Fix indentation Juerg Haefliger
2022-06-09  8:21       ` [PATCH 2/3 v3] ARM: s3c: Kconfig.s3c24xx: Fix indentation and replace some tabs Juerg Haefliger
2022-06-09  8:21       ` [PATCH 3/3 v3] ARM: s3c: Kconfig.s3c64xx: Fix indentation Juerg Haefliger
2022-06-09 18:36       ` [PATCH 0/3 v3] ARM: s3c: Kconfig: Style cleanups Krzysztof Kozlowski

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=20220607085911.4b0f7f10@smeagol \
    --to=juerg.haefliger@canonical.com \
    --cc=alim.akhtar@samsung.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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