From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Christian Marangi <ansuelsmth@gmail.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
Baolin Wang <baolin.wang7@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 2/3] ARM: dts: qcom: add missing hwlock for ipq8064 dtsi
Date: Thu, 7 Jul 2022 08:58:52 +0200 [thread overview]
Message-ID: <95062dd8-0bc3-c350-7fd1-a02dfc4ef1d7@linaro.org> (raw)
In-Reply-To: <20220707013017.26654-2-ansuelsmth@gmail.com>
On 07/07/2022 03:30, Christian Marangi wrote:
> Add missing hwlock for ipq8064 dtsi provided by qcom,sfpb-mutex.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-07 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 1:30 [PATCH 1/3] hwspinlock: qcom: Add support for mmio usage to sfpb-mutex Christian Marangi
2022-07-07 1:30 ` [PATCH 2/3] ARM: dts: qcom: add missing hwlock for ipq8064 dtsi Christian Marangi
2022-07-07 6:58 ` Krzysztof Kozlowski [this message]
2022-07-07 1:30 ` [PATCH 3/3] ARM: dts: qcom: add missing smem compatible " Christian Marangi
2022-07-07 6:59 ` Krzysztof Kozlowski
2022-07-07 6:59 ` Krzysztof Kozlowski
2022-07-07 1:30 ` [PATCH 3/3] ARM: dts: qcom: add missing smem node " Christian Marangi
2022-07-07 1:32 ` Christian Marangi
2022-07-07 2:53 ` [PATCH 1/3] hwspinlock: qcom: Add support for mmio usage to sfpb-mutex Bjorn Andersson
2022-07-07 10:14 ` Christian Marangi
2022-07-07 11:00 ` Baolin Wang
2022-07-07 11:07 ` Christian Marangi
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=95062dd8-0bc3-c350-7fd1-a02dfc4ef1d7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=baolin.wang7@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).