From: Krzysztof Kozlowski <krzk@kernel.org>
To: Violet <violet@atl.tools>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
Date: Thu, 17 Jul 2025 08:16:10 +0200 [thread overview]
Message-ID: <20250717-devious-resourceful-spaniel-6ffad7@kuoka> (raw)
In-Reply-To: <20250716231710.99983-1-violet@atl.tools>
On Wed, Jul 16, 2025 at 11:17:08PM +0000, Violet wrote:
> Changes in v6:
> - Remove debug features (bootargs, etc) that slipped in the v5 DTS
> - Format and organize nodes correctly based on existing DTS,
> move "status = "okay";" to the bottom always
> - Solve "ddr_device_type" and "qcom,rmtfs-mem" warnings, the rest are
> from existing SoC .dtsi
> - Disable buttons, ufs and other features for later revision
How this can be v6? Someone (you?) sent last time v2?
Where is the rest of changelog? v1, v2, v3, v4, v5? Or at least lore
links to previous discussions and changelogs?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-17 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 23:17 [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
2025-07-16 23:17 ` [PATCH v6 1/2] dt-bindings: arm: qcom: document r0q board binding Violet
2025-07-17 14:26 ` Krzysztof Kozlowski
2025-07-16 23:17 ` [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
2025-07-17 14:26 ` Krzysztof Kozlowski
2025-07-17 20:19 ` Konrad Dybcio
2025-07-29 11:46 ` Violet
2025-07-17 6:16 ` Krzysztof Kozlowski [this message]
2025-07-17 15:56 ` [PATCH v6 0/2] " Rob Herring (Arm)
2025-07-30 9:21 ` Pavel Machek
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=20250717-devious-resourceful-spaniel-6ffad7@kuoka \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=violet@atl.tools \
/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).