From: "Matti Lehtimäki" <matti.lehtimaki@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: pinctrl: msm8226: Add General Purpose clocks
Date: Fri, 6 Jan 2023 14:41:20 +0200 [thread overview]
Message-ID: <2a6748b5-df3b-b3a7-f17a-664aab030b48@gmail.com> (raw)
In-Reply-To: <b866e6e1-da10-9152-8bda-966015998877@linaro.org>
On 6.1.2023 14.32, Krzysztof Kozlowski wrote:
> On 06/01/2023 12:44, Matti Lehtimäki wrote:
>> + blsp_uart3, blsp_uart4, blsp_uart5, cam_mclk0,
>> cam_mclk1, + gp0_clk, gp1_clk, sdc3, wlan ]
>
> Driver does not support them (and there is no driver change, unless
> you cc-ed people selectively...).
The driver changes are in patch number 2 of the series, I used
git send-mail with a cc script, which uses get_maintainer.pl to
get the needed addresses for each patch, to send the patches. It
probably didn't send every patch to everyone and would need some
improvement.
-Matti
next prev parent reply other threads:[~2023-01-06 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 11:44 [PATCH 0/3] General Purpose clocks and matisse-wifi backlight Matti Lehtimäki
2023-01-06 11:44 ` [PATCH 1/3] dt-bindings: pinctrl: msm8226: Add General Purpose clocks Matti Lehtimäki
2023-01-06 12:32 ` Krzysztof Kozlowski
2023-01-06 12:41 ` Matti Lehtimäki [this message]
2023-01-06 13:00 ` Krzysztof Kozlowski
2023-01-06 13:00 ` Krzysztof Kozlowski
2023-01-10 7:57 ` Linus Walleij
2023-01-06 11:44 ` [PATCH 2/3] pinctrl: qcom: " Matti Lehtimäki
2023-01-10 7:57 ` Linus Walleij
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=2a6748b5-df3b-b3a7-f17a-664aab030b48@gmail.com \
--to=matti.lehtimaki@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.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=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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).