From: Krzysztof Kozlowski <krzk@kernel.org>
To: setotau@yandex.ru, Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Richard Acayan <mailingradian@gmail.com>
Subject: Re: [PATCH v4 2/3] dt-bindings: pinctrl: qcom: Add SDM660 LPI pinctrl
Date: Fri, 29 Aug 2025 08:07:34 +0200 [thread overview]
Message-ID: <4420d5fe-a847-4def-9ad0-ba39ad6f6b5d@kernel.org> (raw)
In-Reply-To: <fcd25026-97f0-472a-a274-af342b1dce9c@kernel.org>
On 29/08/2025 08:06, Krzysztof Kozlowski wrote:
> On 28/08/2025 21:23, Nickolay Goppen via B4 Relay wrote:
>> From: Nickolay Goppen <setotau@yandex.ru>
>>
>> Add bindings for pin controller in SDM660 Low Power Audio SubSystem
>> LPASS).
>>
>> Co-developed-by: Richard Acayan <mailingradian@gmail.com>
>> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
>> Signed-off-by: Nickolay Goppen <setotau@yandex.ru>
>
> Completely reversed/messed chain.
Ah no, sorry, it's ok. I missed who is the sender here.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-29 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 19:23 [PATCH v4 0/3] Add SDM660 LPASS LPI TLMM Nickolay Goppen via B4 Relay
2025-08-28 19:23 ` [PATCH v4 1/3] pinctrl: qcom: lpass-lpi: Add ability to use custom pin offsets Nickolay Goppen via B4 Relay
2025-08-28 19:23 ` [PATCH v4 2/3] dt-bindings: pinctrl: qcom: Add SDM660 LPI pinctrl Nickolay Goppen via B4 Relay
2025-08-29 6:06 ` Krzysztof Kozlowski
2025-08-29 6:07 ` Krzysztof Kozlowski [this message]
2025-08-29 17:19 ` Nickolay Goppen
2025-08-28 19:23 ` [PATCH v4 3/3] pinctrl: qcom: Add SDM660 LPASS LPI TLMM Nickolay Goppen via B4 Relay
2025-09-03 11:44 ` Konrad Dybcio
2025-09-03 11:47 ` Konrad Dybcio
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=4420d5fe-a847-4def-9ad0-ba39ad6f6b5d@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=robh@kernel.org \
--cc=setotau@yandex.ru \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).