From: Bjorn Andersson <andersson@kernel.org>
To: krzysztof.kozlowski+dt@linaro.org, linux@roeck-us.net,
wim@linux-watchdog.org, robh+dt@kernel.org, agross@kernel.org,
linux-kernel@vger.kernel.org,
Kathiravan T <quic_kathirav@quicinc.com>,
konrad.dybcio@linaro.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: (subset) [PATCH V2 0/2] Add few device nodes for IPQ5332 SoC
Date: Fri, 7 Apr 2023 10:41:17 -0700 [thread overview]
Message-ID: <168088927578.2561591.12316304033286537024.b4-ty@kernel.org> (raw)
In-Reply-To: <20230320104530.30411-1-quic_kathirav@quicinc.com>
On Mon, 20 Mar 2023 16:15:28 +0530, Kathiravan T wrote:
> This series adds the support for QUP peripherals, PRNG, WDT for IPQ5332
> SoC.
>
> This series depends on the below patch, due to the node ordering
> https://lore.kernel.org/linux-arm-msm/20230217083308.12017-6-quic_kathirav@quicinc.com/#t
>
> Kathiravan T (2):
> dt-bindings: watchdog: qcom-wdt: add qcom,apss-wdt-ipq5332 compatible
> arm64: dts: qcom: ipq5332: add few device nodes
>
> [...]
Applied, thanks!
[2/2] arm64: dts: qcom: ipq5332: add few device nodes
commit: d0367098dc1e925d22a6706e358636d12371116c
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-04-07 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 10:45 Kathiravan T
2023-03-20 10:45 ` [PATCH V2 1/2] dt-bindings: watchdog: qcom-wdt: add qcom,apss-wdt-ipq5332 compatible Kathiravan T
2023-04-13 4:39 ` Kathiravan T
2023-04-16 10:19 ` Krzysztof Kozlowski
2023-04-16 15:43 ` Guenter Roeck
2023-03-20 10:45 ` [PATCH V2 2/2] arm64: dts: qcom: ipq5332: add few device nodes Kathiravan T
2023-03-30 15:30 ` [PATCH V2 0/2] Add few device nodes for IPQ5332 SoC Kathiravan T
2023-04-07 17:41 ` 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=168088927578.2561591.12316304033286537024.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=quic_kathirav@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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®