From: Borislav Petkov <bp@alien8.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Marvin Lin <milkfafa@gmail.com>,
robh+dt@kernel.org, tony.luck@intel.com, james.morse@arm.com,
mchehab@kernel.org, rric@kernel.org, benjaminfair@google.com,
yuenn@google.com, venture@google.com, avifishman70@gmail.com,
tmaimon77@gmail.com, tali.perry1@gmail.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
KWLIU@nuvoton.com, YSCHU@nuvoton.com, ctcchien@nuvoton.com,
kflin@nuvoton.com
Subject: Re: [PATCH v18 1/3] ARM: dts: nuvoton: Add node for NPCM memory controller
Date: Mon, 12 Jun 2023 15:16:49 +0200 [thread overview]
Message-ID: <20230612131649.GHZIcawTKBMIQpFD6I@fat_crate.local> (raw)
In-Reply-To: <e0171cb6-54e7-41bd-4b08-fa667fe58ff4@linaro.org>
On Mon, Jun 12, 2023 at 03:00:19PM +0200, Krzysztof Kozlowski wrote:
> No, the DTS is always independent because it describes the hardware.
> Linux should work fine regardless of hardware description. Tying Linux
> to specific DTS is usually sign of an ABI break.
Ok, I see.
Patches 2 and 3 queued for 6.5.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-06-12 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 9:32 [PATCH v18 0/3] EDAC/nuvoton: Add NPCM memory controller driver Marvin Lin
2023-01-11 9:32 ` [PATCH v18 1/3] ARM: dts: nuvoton: Add node for NPCM memory controller Marvin Lin
2023-06-12 11:04 ` Borislav Petkov
2023-06-12 11:22 ` Krzysztof Kozlowski
2023-06-12 12:01 ` Borislav Petkov
2023-06-12 12:09 ` Krzysztof Kozlowski
2023-06-12 12:39 ` Borislav Petkov
2023-06-12 13:00 ` Krzysztof Kozlowski
2023-06-12 13:16 ` Borislav Petkov [this message]
2023-06-13 9:55 ` Kun-Fa Lin
2023-01-11 9:32 ` [PATCH v18 2/3] dt-bindings: memory-controllers: nuvoton: Add " Marvin Lin
2023-01-11 10:54 ` Krzysztof Kozlowski
2023-01-11 9:32 ` [PATCH v18 3/3] EDAC/npcm: Add NPCM memory controller driver Marvin Lin
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=20230612131649.GHZIcawTKBMIQpFD6I@fat_crate.local \
--to=bp@alien8.de \
--cc=KWLIU@nuvoton.com \
--cc=YSCHU@nuvoton.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=ctcchien@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=kflin@nuvoton.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=milkfafa@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=rric@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=tony.luck@intel.com \
--cc=venture@google.com \
--cc=yuenn@google.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