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: Thu, 5 May 2022 16:26:12 +0100 [thread overview]
Message-ID: <YnPslKE9klw/Mair@sirena.org.uk> (raw)
In-Reply-To: <a099eb33-91a0-0262-f6c0-a77dc7aec146@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
On Thu, May 05, 2022 at 11:00:26AM +0200, Krzysztof Kozlowski wrote:
> I don't know, Mark. The confusion was not intended. The second patch in
> the set depended on SPI patch, so probably after three weeks Bjorn just
> took entire set.
> https://lore.kernel.org/all/20220404064017.68634-1-krzysztof.kozlowski@linaro.org/
Ah, so this was part of the pile where I was waiting for Bjorn to say if
he was OK with adding him as a maintainer. Bjorn, please don't just
apply patches without some sort of handshake when people are clearly
around and replying to mail - it causes confusion like this :(
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-05 15:26 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
2022-05-05 9:00 ` Krzysztof Kozlowski
2022-05-05 15:26 ` Mark Brown [this message]
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=YnPslKE9klw/Mair@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