public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Chun Ng <chunn@nvidia.com>,
	linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	thierry.reding@gmail.com, jonathanh@nvidia.com,
	ankitag@nvidia.com
Subject: Re: [PATCH 4/4] arm64: tegra: add e2426-1099+e2423-1099 support
Date: Thu, 26 Mar 2026 12:12:49 +0100	[thread overview]
Message-ID: <cf7566f9-d038-4ddd-bb95-ef350f17aeb9@kernel.org> (raw)
In-Reply-To: <acUQ1mOQ2ajrnUC9@orome>

On 26/03/2026 12:03, Thierry Reding wrote:
> On Thu, Mar 26, 2026 at 11:18:17AM +0100, Krzysztof Kozlowski wrote:
>> On Wed, Mar 25, 2026 at 09:26:28PM +0000, Chun Ng wrote:
>>> Add the Tegra238 SoC device tree (tegra238.dtsi) and a minimal device
>>> tree for the Tegra238 E2426-1099+E2423-1099 engineering reference
>>> platform. The device-tree is not yet bootable and further enablement
>>
>> Then drop it. If this cannot be booted then it is pointless in the
>> kernel, no benefit, no one can ever use it.
> 
> The purpose of this series is to establish a common baseline that people
> can use to work on top off. We expect the non-bootable state to be very
> temporary, but for practical reasons I want to get this merged so we can
> make quicker progress.

If this cannot be booted, then there are no practical reasons - no one
will be able to develop on top of it.

The only way anyone could use it is to have additional patch on top, to
make it booting. Thus if you have already patches on top, which you need
to share with every team/person, then you can as well share this one.

What is the benefit for the community of having this patch in the kernel?
=

Best regards,
Krzysztof

      reply	other threads:[~2026-03-26 11:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 21:26 [PATCH 0/4] arm64: tegra: add initial Tegra238 and E2426-1099+E2423-1099 support Chun Ng
2026-03-25 21:26 ` [PATCH 1/4] dt-bindings: tegra: Add Tegra238 clock and reset definitions Chun Ng
2026-03-26 10:19   ` Krzysztof Kozlowski
2026-03-25 21:26 ` [PATCH 2/4] dt-bindings: tegra: Document E2426-1099+E2423-1099 platform Chun Ng
2026-03-25 21:26 ` [PATCH 3/4] dt-bindings: mailbox: tegra186-hsp: allow doorbell+shared or shared-only Chun Ng
2026-03-26 10:22   ` Krzysztof Kozlowski
2026-03-25 21:26 ` [PATCH 4/4] arm64: tegra: add e2426-1099+e2423-1099 support Chun Ng
2026-03-26 10:18   ` Krzysztof Kozlowski
2026-03-26 11:03     ` Thierry Reding
2026-03-26 11:12       ` Krzysztof Kozlowski [this message]

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=cf7566f9-d038-4ddd-bb95-ef350f17aeb9@kernel.org \
    --to=krzk@kernel.org \
    --cc=ankitag@nvidia.com \
    --cc=chunn@nvidia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox