All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] bus: ti-sysc: Drop commas after SoC match table sentinels
Date: Thu, 21 Apr 2022 15:07:41 +0300	[thread overview]
Message-ID: <YmFJDTeqRcwb5Ucu@atomide.com> (raw)
In-Reply-To: <602f74030dc746eaa9f82f115acc46e62c6be165.1646311501.git.geert+renesas@glider.be>

* Geert Uytterhoeven <geert+renesas@glider.be> [220303 14:44]:
> It does not make sense to have a comma after a sentinel, as any new
> elements must be added before the sentinel.

Applying into omap-for-v5.19/ti-sysc thanks.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] bus: ti-sysc: Drop commas after SoC match table sentinels
Date: Thu, 21 Apr 2022 15:07:41 +0300	[thread overview]
Message-ID: <YmFJDTeqRcwb5Ucu@atomide.com> (raw)
In-Reply-To: <602f74030dc746eaa9f82f115acc46e62c6be165.1646311501.git.geert+renesas@glider.be>

* Geert Uytterhoeven <geert+renesas@glider.be> [220303 14:44]:
> It does not make sense to have a comma after a sentinel, as any new
> elements must be added before the sentinel.

Applying into omap-for-v5.19/ti-sysc thanks.

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-21 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 12:45 [PATCH] bus: ti-sysc: Drop commas after SoC match table sentinels Geert Uytterhoeven
2022-03-03 12:45 ` Geert Uytterhoeven
2022-04-21 12:07 ` Tony Lindgren [this message]
2022-04-21 12:07   ` 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=YmFJDTeqRcwb5Ucu@atomide.com \
    --to=tony@atomide.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    /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.