From: <Conor.Dooley@microchip.com>
To: <u.kleine-koenig@pengutronix.de>, <Conor.Dooley@microchip.com>
Cc: <Daire.McNamara@microchip.com>, <devicetree@vger.kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <lee.jones@linaro.org>,
<linux-kernel@vger.kernel.org>, <linux-pwm@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <robh+dt@kernel.org>,
<thierry.reding@gmail.com>
Subject: Re: [PATCH v7 3/4] pwm: add microchip soft ip corePWM driver
Date: Fri, 5 Aug 2022 20:01:27 +0000 [thread overview]
Message-ID: <428842ed-4070-ced8-e032-bfb48d5af4fe@microchip.com> (raw)
In-Reply-To: <20220805195836.vh3wv4xbpwjhuvfs@pengutronix.de>
On 05/08/2022 20:58, Uwe Kleine-König wrote:
> Hello Conor,
>
> On Tue, Aug 02, 2022 at 12:34:14PM +0000, Conor.Dooley@microchip.com wrote:
>> I'll fix it all up & submit v8 after -rc1.
>
> I discard the whole series in patchwork in the expectation that all
> patches will be part of your v8.
That was my plan, don't think there's a rush on the dt-binding fix.
Thanks Uwe,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-08-05 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 17:21 [PATCH v7 0/4] Microchip soft ip corePWM driver Conor Dooley
2022-07-21 17:21 ` [PATCH v7 1/4] dt-bindings: pwm: fix microchip corePWM's pwm-cells Conor Dooley
2022-08-02 7:45 ` Uwe Kleine-König
2022-07-21 17:21 ` [PATCH v7 2/4] riscv: dts: fix the icicle's #pwm-cells Conor Dooley
2022-08-02 7:43 ` Uwe Kleine-König
2022-07-21 17:21 ` [PATCH v7 3/4] pwm: add microchip soft ip corePWM driver Conor Dooley
2022-08-02 8:46 ` Uwe Kleine-König
2022-08-02 12:34 ` Conor.Dooley
2022-08-05 19:58 ` Uwe Kleine-König
2022-08-05 20:01 ` Conor.Dooley [this message]
2022-07-21 17:21 ` [PATCH v7 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=428842ed-4070-ced8-e032-bfb48d5af4fe@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).