From: Bjorn Andersson <andersson@kernel.org>
To: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
devicetree@vger.kernel.org,
Richard Acayan <mailingradian@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org
Cc: Odelu Kukatla <quic_okukatla@quicinc.com>, Luca Weiss <luca@z3ntu.xyz>
Subject: Re: [PATCH v4 0/2] SDM670 Interconnects (now with dts patches only)
Date: Wed, 8 Feb 2023 20:23:19 -0800 [thread overview]
Message-ID: <167591660369.1230100.10064457807508339752.b4-ty@kernel.org> (raw)
In-Reply-To: <20230201010020.84586-1-mailingradian@gmail.com>
On Tue, 31 Jan 2023 20:00:18 -0500, Richard Acayan wrote:
> Changes since v4 (20230111005155.50452-1-mailingradian@gmail.com):
> - drop applied bindings and driver patches (previously 1-2/4)
>
> Changes since v3:
> - fix a merge conflict on linux-next (1/4)
>
> Changes since v2:
> - change qcom,sdm670.h to qcom,sdm670-rpmh.h (2/4)
> - use SPDX v3 license identifiers (1/4, 2/4)
> - accumulate ack tag (1/4)
> - format changelog (0/4)
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: sdm670: add interconnects
commit: 0daef104e4b1d945ac81cb10e35c29f82695b10a
[2/2] arm64: dts: qcom: sdm670: add opps for peripherals
(no commit info)
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
next prev parent reply other threads:[~2023-02-09 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 1:00 [PATCH v4 0/2] SDM670 Interconnects (now with dts patches only) Richard Acayan
2023-02-01 1:00 ` [PATCH v4 1/2] arm64: dts: qcom: sdm670: add interconnects Richard Acayan
2023-02-01 1:00 ` [PATCH v4 2/2] arm64: dts: qcom: sdm670: add opps for peripherals Richard Acayan
2023-02-01 18:51 ` Konrad Dybcio
2023-02-09 4:23 ` Bjorn Andersson [this message]
2023-03-15 23:35 ` (subset) [PATCH v4 0/2] SDM670 Interconnects (now with dts patches only) 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=167591660369.1230100.10064457807508339752.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=luca@z3ntu.xyz \
--cc=mailingradian@gmail.com \
--cc=quic_okukatla@quicinc.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.