All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Devang Tailor <dev.tailor@samsung.com>,
	alexandre.belloni@bootlin.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, alim.akhtar@samsung.com,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	inux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, faraz.ata@samsung.com
Subject: Re: [PATCH 3/3] arm64: dts: exynosautov9: add RTC DT node
Date: Mon, 7 Jul 2025 11:23:09 +0200	[thread overview]
Message-ID: <46fb0a9d-be33-46c6-98d1-501970ec8e7a@kernel.org> (raw)
In-Reply-To: <20250702052426.2404256-4-dev.tailor@samsung.com>

On 02/07/2025 07:24, Devang Tailor wrote:
> --- a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi
> +++ b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi
> @@ -1633,6 +1633,16 @@ pwm: pwm@103f0000 {
>  			clock-names = "timers";
>  			status = "disabled";
>  		};
> +
> +		rtc: rtc@10540000 {
> +			compatible = "samsung,exynosautov9-rtc";
> +			reg = <0x10540000 0x100>;
> +			interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>,
> +				<GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>;


Misaligned. Should match earlier '<'.


Best regards,
Krzysztof

  reply	other threads:[~2025-07-07  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250702051528epcas5p24abd15d8f554ea057bd6aac586644f4e@epcas5p2.samsung.com>
2025-07-02  5:24 ` [PATCH 0/3] On-chip RTC support for ExynosAutov9 Devang Tailor
2025-07-02  5:24   ` [PATCH 1/3] dt-bindings: rtc: s3c-rtc: add compatible for exynosautov9 Devang Tailor
2025-07-07  9:16     ` Krzysztof Kozlowski
2025-07-02  5:24   ` [PATCH 2/3] rtc: s3c: support for exynosautov9 on-chip RTC Devang Tailor
2025-07-07  9:23     ` Krzysztof Kozlowski
2025-07-08  5:03       ` Devang Tailor
2025-07-02  5:24   ` [PATCH 3/3] arm64: dts: exynosautov9: add RTC DT node Devang Tailor
2025-07-07  9:23     ` Krzysztof Kozlowski [this message]
2025-07-08  5:00       ` Devang Tailor

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=46fb0a9d-be33-46c6-98d1-501970ec8e7a@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=dev.tailor@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=faraz.ata@samsung.com \
    --cc=inux-arm-kernel@lists.infradead.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh@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.