From: <Conor.Dooley@microchip.com>
To: <thierry.reding@gmail.com>, <u.kleine-koenig@pengutronix.de>,
<lee.jones@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <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 11:05:54 +0000 [thread overview]
Message-ID: <ee05749f-c33f-3505-4309-f4d036de92a1@microchip.com> (raw)
In-Reply-To: <c49776c2-4807-91c1-010a-a33bd98b68b7@microchip.com>
On 13/07/2022 09:54, Conor Dooley - M52691 wrote:
> On 12/07/2022 15:25, Conor Dooley wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> Add a driver that supports the Microchip FPGA "soft" PWM IP core.
>
> Looks like there's a couple W=1 warnings about the mutex use, I'll not respin
> until you've had a chance to have a look at this version.
> Thanks,
> Conor.
Hey Uwe,
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.
Thanks,
Conor.
next prev parent reply other threads:[~2022-07-21 11:06 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 [this message]
2022-07-21 14:20 ` Uwe Kleine-König
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=ee05749f-c33f-3505-4309-f4d036de92a1@microchip.com \
--to=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 \
--cc=u.kleine-koenig@pengutronix.de \
/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).