All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: renesas: Add missing space after remote-endpoint
Date: Thu, 9 Jun 2022 11:23:48 +0200	[thread overview]
Message-ID: <CAMuHMdVr1h1gPAJneJOQ5qPDFeRA_6hRt1ijUNa0nOtYRjLm1w@mail.gmail.com> (raw)
In-Reply-To: <YqGyCtmLM9vl4voC@oden.dyn.berto.se>

Hi Niklas,

On Thu, Jun 9, 2022 at 10:40 AM Niklas Söderlund
<niklas.soderlund+renesas@ragnatech.se> wrote:
> On 2022-06-09 10:13:49 +0200, Geert Uytterhoeven wrote:
> > On Wed, Jun 8, 2022 at 7:58 PM Niklas Söderlund
> > <niklas.soderlund+renesas@ragnatech.se> wrote:
> > > Add the missing space after remote-endpoint in r8a774c0.dtsi and
> > > r8a77990.dtsi before the typo spreads to other files.
> > >
> > > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>

> > Do you plan to fix the other in-tree offenders, too?
>
> I was plain too, seems like a perfect opportunity to force myself to try
> and learn Coccinelle :-)

Very smart!
I would chicken-out, saying the number of offenders is too small ;-)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2022-06-09  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 17:57 [PATCH] arm64: dts: renesas: Add missing space after remote-endpoint Niklas Söderlund
2022-06-09  8:13 ` Geert Uytterhoeven
2022-06-09  8:40   ` Niklas Söderlund
2022-06-09  9:23     ` Geert Uytterhoeven [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=CAMuHMdVr1h1gPAJneJOQ5qPDFeRA_6hRt1ijUNa0nOtYRjLm1w@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    /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.