From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Conor Dooley <conor@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v13 2/2] MAINTAINERS: add pwm to PolarFire SoC entry
Date: Tue, 10 Jan 2023 23:50:05 +0100 [thread overview]
Message-ID: <20230110225005.vp5p2i54baxzbugo@pengutronix.de> (raw)
In-Reply-To: <20221221112912.147210-3-conor@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
Hello,
On Wed, Dec 21, 2022 at 11:29:13AM +0000, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Add the newly introduced pwm driver to the existing PolarFire SoC entry.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
the patch looks fine, but as the first patch has to change, I'm
discarding this one from the PWM patchwork, too.
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 --]
prev parent reply other threads:[~2023-01-10 22:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 11:29 [PATCH v13 0/2] Microchip Soft IP corePWM driver Conor Dooley
2022-12-21 11:29 ` [PATCH v13 1/2] pwm: add microchip soft ip " Conor Dooley
2023-01-10 22:48 ` Uwe Kleine-König
2023-01-11 0:15 ` Conor Dooley
2023-01-11 7:02 ` Uwe Kleine-König
2023-01-11 8:00 ` Conor Dooley
2023-01-11 9:15 ` Uwe Kleine-König
2023-01-11 9:24 ` Uwe Kleine-König
2023-01-12 12:01 ` Uwe Kleine-König
2023-01-12 15:10 ` Conor Dooley
2023-01-20 19:40 ` Conor Dooley
2023-02-13 12:45 ` Conor Dooley
2022-12-21 11:29 ` [PATCH v13 2/2] MAINTAINERS: add pwm to PolarFire SoC entry Conor Dooley
2023-01-10 22:50 ` Uwe Kleine-König [this message]
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=20230110225005.vp5p2i54baxzbugo@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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).