From: Gabriel Gonzales <semfault@disroot.org>
To: konrad.dybcio@oss.qualcomm.com
Cc: andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, gpiccoli@igalia.com, kees@kernel.org,
konradybcio@kernel.org, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
semfault@disroot.org, tony.luck@intel.com
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: sm6125: Initial support for xiaomi-ginkgo
Date: Tue, 11 Mar 2025 08:18:46 +0800 [thread overview]
Message-ID: <7f4cb66c-92f8-445a-8d29-4afd1dd0b9c3@disroot.org> (raw)
In-Reply-To: <455b685e-0ccc-4c57-a60f-39ff9cd280ca@oss.qualcomm.com>
On 3/11/25 07:37, Konrad Dybcio wrote:
> > 'a-status'?
> A newline.. the brain didn't synchronize with the hands
How about nodes which only have 'status' as a property name? Do they
still need to be placed before a NL or keep as-is?
next prev parent reply other threads:[~2025-03-11 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250304043742.9252-1-semfault@disroot.org>
2025-03-04 4:37 ` [PATCH v1 2/2] arm64: dts: qcom: sm6125: Initial support for xiaomi-ginkgo Gabriel Gonzales
2025-03-08 1:30 ` [PATCH v2 0/2] Add Xiaomi Redmi Note 8 support Gabriel Gonzales
2025-03-08 1:30 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Add Xiaomi Redmi Note 8 Gabriel Gonzales
2025-03-10 9:46 ` Krzysztof Kozlowski
2025-03-08 1:30 ` [PATCH v2 2/2] arm64: dts: qcom: sm6125: Initial support for xiaomi-ginkgo Gabriel Gonzales
2025-03-08 15:11 ` Konrad Dybcio
2025-03-10 23:28 ` Gabriel Gonzales
2025-03-10 23:37 ` Konrad Dybcio
2025-03-11 0:18 ` Gabriel Gonzales [this message]
2025-03-10 14:36 ` [PATCH v2 0/2] Add Xiaomi Redmi Note 8 support Rob Herring (Arm)
[not found] ` <20250311003353.8250-1-semfault@disroot.org>
2025-03-11 0:33 ` [PATCH v3 2/2] arm64: dts: qcom: sm6125: Initial support for xiaomi-ginkgo Gabriel Gonzales
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=7f4cb66c-92f8-445a-8d29-4afd1dd0b9c3@disroot.org \
--to=semfault@disroot.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony.luck@intel.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