mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Franziska Naepelt <franziska.naepelt@googlemail.com>,
	linux-arm-kernel@lists.infradead.org
Cc: hsweeten@visionengravers.com, linux@armlinux.org.uk,
	linux-kernel@vger.kernel.org,
	Franziska Naepelt <franziska.naepelt@gmail.com>
Subject: Re: [PATCH] ARM: ep93xx: Fix whitespace issues
Date: Mon, 29 May 2023 17:19:36 +0200	[thread overview]
Message-ID: <873fc37f5fc9ed04698c99feafca156699b2b1ee.camel@gmail.com> (raw)
In-Reply-To: <20230529143333.19278-1-franziska.naepelt@gmail.com>

Hello Franziska,

On Mon, 2023-05-29 at 16:33 +0200, Franziska Naepelt wrote:
> This removes the following checkpatch issues:
> - ERROR: code indent should use tabs where possible
> - WARNING: please, no spaces at the start of a line
> 
> Signed-off-by: Franziska Naepelt <franziska.naepelt@gmail.com>

thanks for the patch!
However the file is going away at some point anyway:
https://lore.kernel.org/lkml/20230424123522.18302-40-nikita.shubin@maquefel.me/

> ---
>  arch/arm/mach-ep93xx/timer-ep93xx.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/mach-ep93xx/timer-ep93xx.c b/arch/arm/mach-ep93xx/timer-ep93xx.c
> index dd4b164d1831..5bfabbdde463 100644
> --- a/arch/arm/mach-ep93xx/timer-ep93xx.c
> +++ b/arch/arm/mach-ep93xx/timer-ep93xx.c
> @@ -82,8 +82,8 @@ static int ep93xx_clkevt_set_next_event(unsigned long next,
>         /* Set next event */
>         writel(next, EP93XX_TIMER3_LOAD);
>         writel(tmode | EP93XX_TIMER123_CONTROL_ENABLE,
> -              EP93XX_TIMER3_CONTROL);
> -        return 0;
> +                  EP93XX_TIMER3_CONTROL);
> +       return 0;
>  }
>  

-- 
Alexander Sverdlin.


  reply	other threads:[~2023-05-29 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 14:33 Franziska Naepelt
2023-05-29 15:19 ` Alexander Sverdlin [this message]
2023-05-30  4:27   ` Franziska Näpelt

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=873fc37f5fc9ed04698c99feafca156699b2b1ee.camel@gmail.com \
    --to=alexander.sverdlin@gmail.com \
    --cc=franziska.naepelt@gmail.com \
    --cc=franziska.naepelt@googlemail.com \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®