From: Jie Gan <quic_jiegan@quicinc.com>
To: Varadarajan Narayanan <quic_varada@quicinc.com>,
<andersson@kernel.org>, <konradybcio@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<dmitry.baryshkov@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/1] Fix USB vdd info for IPQ9574
Date: Fri, 7 Feb 2025 16:56:35 +0800 [thread overview]
Message-ID: <de8fc55c-2d68-490b-9a12-cb368e27d266@quicinc.com> (raw)
In-Reply-To: <20250207073545.1768990-1-quic_varada@quicinc.com>
On 2/7/2025 3:35 PM, Varadarajan Narayanan wrote:
> Use correct regulator for USB phy.
>
> v2: * Skip the first patch as it has been pulled in
> * Reword and fix commit message formatting for the remaining patch
>
You dont need the cover letter patch if you only have one patch.
B4 can handle it automatically.
Thanks,
Jie
> v1: For some reason, the dt-bindings [1] patch posted and Acked long
> time back seems to have slipped through the cracks and hasn't been
> merged. Including it along with this patch as both are related.
> dt_binding_check & dtbs_check passed.
>
> 1 - https://lore.kernel.org/linux-arm-msm/170266996013.286103.17303148912355511017.robh@kernel.org/
>
> Varadarajan Narayanan (1):
> arm64: dts: qcom: ipq9574: Fix USB vdd info
>
> arch/arm64/boot/dts/qcom/ipq9574-rdp-common.dtsi | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
>
> base-commit: 40b8e93e17bff4a4e0cc129e04f9fdf5daa5397e
> prerequisite-patch-id: d3da55704446c2222b5c624d9bb3a738357cb2fc
next prev parent reply other threads:[~2025-02-07 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 7:35 Varadarajan Narayanan
2025-02-07 7:35 ` [PATCH v2 1/1] arm64: dts: qcom: ipq9574: Fix USB vdd info Varadarajan Narayanan
2025-02-10 19:08 ` Konrad Dybcio
2025-02-07 8:56 ` Jie Gan [this message]
2025-03-17 2:55 ` (subset) [PATCH v2 0/1] Fix USB vdd info for IPQ9574 Bjorn Andersson
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=de8fc55c-2d68-490b-9a12-cb368e27d266@quicinc.com \
--to=quic_jiegan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_varada@quicinc.com \
--cc=robh@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
all inboxes | Powered by JetHome®