public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: "William A. Kennington III" <william@wkennington.com>,
	Avi Fishman <avifishman70@gmail.com>,
	Tomer Maimon <tmaimon77@gmail.com>,
	Tali Perry <tali.perry1@gmail.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: nuvoton: Add EDAC controller
Date: Wed, 07 May 2025 12:22:08 +0930	[thread overview]
Message-ID: <2ed50b1463f62a829f863b889ab818f492b73946.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250415233403.2052913-1-william@wkennington.com>

On Tue, 2025-04-15 at 16:34 -0700, William A. Kennington III wrote:
> We have the driver support but need a common node for all the 8xx
> platforms that contain this device.
> 
> Signed-off-by: William A. Kennington III <william@wkennington.com>
> ---
>  arch/arm64/boot/dts/nuvoton/nuvoton-common-npcm8xx.dtsi | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/nuvoton/nuvoton-common-npcm8xx.dtsi b/arch/arm64/boot/dts/nuvoton/nuvoton-common-npcm8xx.dtsi
> index 4da62308b274..ccebcb11c05e 100644
> --- a/arch/arm64/boot/dts/nuvoton/nuvoton-common-npcm8xx.dtsi
> +++ b/arch/arm64/boot/dts/nuvoton/nuvoton-common-npcm8xx.dtsi
> @@ -56,6 +56,13 @@ clk: rstc: reset-controller@f0801000 {
>                         #clock-cells = <1>;
>                 };
>  
> +               mc: memory-controller@f0824000 {
> +                       compatible = "nuvoton,npcm845-memory-controller";
> +                       reg = <0x0 0xf0824000 0x0 0x2000>;
> +                       interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
> +                       status = "disabled";
> +               };
> +

The patch fails to apply due to fuzz, do you mind rebasing it on
nuvoton/arm64/dt from [1]?

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/arj/bmc.git

Possibly it's the result of applying other patches of yours as they
were sent independently. It might be best to send them as a series even
if they are conceptually independent.

Andrew

  reply	other threads:[~2025-05-07  2:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 23:34 [PATCH] arm64: dts: nuvoton: Add EDAC controller William A. Kennington III
2025-05-07  2:52 ` Andrew Jeffery [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-16  0:13 William A. Kennington III
2025-04-16  6:52 ` Krzysztof Kozlowski
2025-04-25 21:23   ` William Kennington
2025-04-27 19:02     ` Krzysztof Kozlowski

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=2ed50b1463f62a829f863b889ab818f492b73946.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=avifishman70@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=robh@kernel.org \
    --cc=tali.perry1@gmail.com \
    --cc=tmaimon77@gmail.com \
    --cc=william@wkennington.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