From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Nylon Chen <nylon.chen@sifive.com>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
thierry.reding@gmail.com, u.kleine-koenig@pengutronix.de,
emil.renner.berthing@canonical.com, vincent.chen@sifive.com
Cc: greentime.hu@sifive.com, zong.li@sifive.com, nylon7717@gmail.com
Subject: Re: [v5 2/2] pwm: sifive: change the PWM controlled LED algorithm
Date: Thu, 9 Nov 2023 09:22:00 +0100 [thread overview]
Message-ID: <21985579-e017-4a56-b5e3-697fd9d0c9d7@linaro.org> (raw)
In-Reply-To: <CAHh=Yk_i-tH-n_5wuwp6H8QRu3cZovkukDzMbeUZrgiih46V8g@mail.gmail.com>
On 09/11/2023 08:02, Nylon Chen wrote:
> Hi, Ping on the series.
>
> Uwe, is there anything more I can do to push the process forward?
It's merge window. What do you exactly expect to happen?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-09 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 10:19 [v5 0/2] Change PWM-controlled LED pin active mode and algorithm Nylon Chen
2023-10-24 10:19 ` [v5 1/2] riscv: dts: sifive: unleashed/unmatched: Remove PWM controlled LED's active-low properties Nylon Chen
2023-10-24 14:55 ` Conor Dooley
2023-10-25 9:32 ` Nylon Chen
2023-10-25 14:14 ` Conor Dooley
2023-10-27 8:54 ` Nylon Chen
2023-12-11 20:42 ` Uwe Kleine-König
2023-10-24 10:19 ` [v5 2/2] pwm: sifive: change the PWM controlled LED algorithm Nylon Chen
2023-11-09 7:02 ` Nylon Chen
2023-11-09 8:22 ` Krzysztof Kozlowski [this message]
2023-12-06 2:35 ` Nylon Chen
2023-12-11 20:49 ` Uwe Kleine-König
2024-01-08 8:27 ` Nylon Chen
2024-01-08 9:25 ` Uwe Kleine-König
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=21985579-e017-4a56-b5e3-697fd9d0c9d7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=greentime.hu@sifive.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nylon.chen@sifive.com \
--cc=nylon7717@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vincent.chen@sifive.com \
--cc=zong.li@sifive.com \
/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