From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: dt-bindings: qcom,spi-geni-qcom: allow three interconnects
Date: Wed, 4 May 2022 16:20:40 +0100 [thread overview]
Message-ID: <YnKZyCogvngR7zfc@sirena.org.uk> (raw)
In-Reply-To: <cfba178d-ff36-910b-3067-ce32b701b643@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
On Wed, May 04, 2022 at 05:14:19PM +0200, Krzysztof Kozlowski wrote:
> On 04/05/2022 17:01, Mark Brown wrote:
> > On Wed, May 04, 2022 at 02:51:19PM +0200, Krzysztof Kozlowski wrote:
> >> Recent Qualcomm Geni SPI nodes, e.g. on SM8450, come with three
> >> interconnects. This fixes dtbs_check warnings like:
> > This doesn't apply against current code, please check and resend.
> Thanks Mark, but as explained in commit below "---" - this is a fix for
> commit in Qualcomm/Bjorn tree. Could you ack it instead?
I was expecting this to be a fix for some change in the DTs in the
Qualcomm tree. Why is there a change to the SPI bindings in there? I
don't seem to have reviewed it...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-04 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 12:51 [PATCH] spi: dt-bindings: qcom,spi-geni-qcom: allow three interconnects Krzysztof Kozlowski
2022-05-04 15:01 ` Mark Brown
2022-05-04 15:14 ` Krzysztof Kozlowski
2022-05-04 15:20 ` Mark Brown [this message]
2022-05-05 9:00 ` Krzysztof Kozlowski
2022-05-05 15:26 ` Mark Brown
2022-05-04 15:37 ` Rob Herring
2022-05-05 6:50 ` Krzysztof Kozlowski
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=YnKZyCogvngR7zfc@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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).