From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Conor.Dooley@microchip.com
Cc: thierry.reding@gmail.com, lee.jones@linaro.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
Daire.McNamara@microchip.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v6 3/4] pwm: add microchip soft ip corePWM driver
Date: Thu, 21 Jul 2022 16:20:30 +0200 [thread overview]
Message-ID: <20220721142030.yh7x3ebr2b4fcunc@pengutronix.de> (raw)
In-Reply-To: <ee05749f-c33f-3505-4309-f4d036de92a1@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
Hello,
On Thu, Jul 21, 2022 at 11:05:54AM +0000, Conor.Dooley@microchip.com wrote:
> Should I resubmit now with the warnings fixed?
> It is a pair of unused-result on the mutexes & a unused-variable so
> they should not have much of an impact on any review you would give
> for this version.
Don't wait for me to find the time to look. If you have some pending
changes I prefer not to look at the series with known drawbacks.
So fire at will.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-21 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 14:25 [PATCH v6 0/4] Microchip soft ip corePWM driver Conor Dooley
2022-07-12 14:25 ` [PATCH v6 1/4] dt-bindings: pwm: fix microchip corePWM's pwm-cells Conor Dooley
2022-07-12 14:25 ` [PATCH v6 2/4] riscv: dts: fix the icicle's #pwm-cells Conor Dooley
2022-07-12 14:25 ` [PATCH v6 3/4] pwm: add microchip soft ip corePWM driver Conor Dooley
2022-07-13 8:54 ` Conor.Dooley
2022-07-21 11:05 ` Conor.Dooley
2022-07-21 14:20 ` Uwe Kleine-König [this message]
2022-07-21 14:30 ` Conor Dooley
2022-07-12 14:25 ` [PATCH v6 4/4] MAINTAINERS: add pwm to PolarFire SoC entry Conor Dooley
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=20220721142030.yh7x3ebr2b4fcunc@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Conor.Dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).