devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4] ARM: dts: renesas: rskrza1: use interrupts-extended for gpio-keys
Date: Fri, 27 Sep 2024 14:30:11 +0200	[thread overview]
Message-ID: <771ca057-af25-475a-8f2f-374a150134e3@kernel.org> (raw)
In-Reply-To: <20240927095414.10241-9-wsa+renesas@sang-engineering.com>

On 27/09/2024 11:54, Wolfram Sang wrote:
> Use the more concise interrupts-extended property to fully describe the
> interrupt.
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---

The code is correct, but are you sure this is not just a churn?

Best regards,
Krzysztof


  reply	other threads:[~2024-09-27 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  9:54 [PATCH 0/4] ARM: dts: renesas: use interrupts-extended for gpio-keys Wolfram Sang
2024-09-27  9:54 ` [PATCH 1/4] ARM: dts: renesas: marzen: " Wolfram Sang
2024-09-27 12:29   ` Krzysztof Kozlowski
2024-09-30 14:27   ` Geert Uytterhoeven
2024-09-27  9:54 ` [PATCH 2/4] ARM: dts: renesas: genmai: " Wolfram Sang
2024-09-27 12:29   ` Krzysztof Kozlowski
2024-09-30 14:29   ` Geert Uytterhoeven
2024-09-27  9:54 ` [PATCH 3/4] ARM: dts: renesas: rskrza1: " Wolfram Sang
2024-09-27 12:30   ` Krzysztof Kozlowski [this message]
2024-09-30 14:38     ` Wolfram Sang
2024-09-30 14:29   ` Geert Uytterhoeven
2024-09-27  9:54 ` [PATCH 4/4] ARM: dts: renesas: rza2mevb: " Wolfram Sang
2024-09-30 14:30   ` Geert Uytterhoeven

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=771ca057-af25-475a-8f2f-374a150134e3@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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;
as well as URLs for NNTP newsgroup(s).