From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Caleb Connolly <caleb@postmarketos.org>,
Alexander Martinz <amartinz@shiftphones.com>,
Luca Weiss <luca.weiss@fairphone.com>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Name the regulators for QCM6490 Fairphone 5 & SHIFTphone 8
Date: Fri, 21 Jun 2024 01:11:22 -0500 [thread overview]
Message-ID: <171895028802.12506.5589187790199098753.b4-ty@kernel.org> (raw)
In-Reply-To: <20240618-qcm6490-regulator-name-v1-0-69fa05e9f58e@fairphone.com>
On Tue, 18 Jun 2024 15:30:53 +0200, Luca Weiss wrote:
> As per individual commit messages:
>
> Without explicitly specifying names for the regulators they are named
> based on the DeviceTree node name. This results in multiple regulators
> with the same name, making debug prints and regulator_summary impossible
> to reason about.
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: qcm6490-fairphone-fp5: Name the regulators
commit: 4c3849513fa1b4d9f6fbe08ecd65e2d6ae19c1fb
[2/2] arm64: dts: qcom: qcm6490-shift-otter: Name the regulators
commit: e160c41b96b6d6f38b8646e3c914c630da21e105
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-06-21 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 13:30 Luca Weiss
2024-06-18 13:30 ` [PATCH 1/2] arm64: dts: qcom: qcm6490-fairphone-fp5: Name the regulators Luca Weiss
2024-06-18 13:35 ` Konrad Dybcio
2024-06-18 13:30 ` [PATCH 2/2] arm64: dts: qcom: qcm6490-shift-otter: " Luca Weiss
2024-06-18 13:35 ` Konrad Dybcio
2024-06-18 15:05 ` Caleb Connolly
2024-06-21 6:11 ` Bjorn Andersson [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=171895028802.12506.5589187790199098753.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=amartinz@shiftphones.com \
--cc=caleb@postmarketos.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®