From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Jeremy Clifton <deaner92@yahoo.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: pwm: Convert NXP PCA9685 PWM controller to DT schema
Date: Wed, 21 Oct 2026 07:56:50 +0200 [thread overview]
Message-ID: <athTVpsanlK9_mVJ@monoceros> (raw)
In-Reply-To: <8365f405-2686-4ea3-b216-7928b826f6a1@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
Hello,
On Tue, Oct 20, 2026 at 09:13:26AM -0600, Jeremy Clifton wrote:
> On 10/16/26 4:33 AM, Uwe Kleine-König wrote:
> > On Mon, Oct 12, 2026 at 02:03:46PM +0000, Jeremy Dean Clifton wrote:
> > > +maintainers:
> > > + - Jeremy Dean Clifton <deaner92@yahoo.com>
> >
> > What kind of commitment do you plan for this maintainer role? Do you
> > have the hardware?
>
> I don't have the hardware, but I'm willing to get it and test on
> it if it comes to that. I'm glad to answer questions about the binding
> and to review future changes to it, also.
>
> If you'd rather have someone closer to the driver listed as maintainer
> instead, that's fine with me too. I'm happy with either possibility.
I want that role combinded with the driver maintenance, so for now let's
put me. If you want to take a responsibility here, please start working
on it. With a track record you can take maintainership at a later point
in time.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-10-21 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261012140346.3065-1-deaner92.ref@yahoo.com>
2026-10-12 14:03 ` Jeremy Dean Clifton
2026-10-15 20:23 ` Rob Herring (Arm)
2026-10-16 10:33 ` Uwe Kleine-König
2026-10-20 15:13 ` Jeremy Clifton
2026-10-21 5:56 ` 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=athTVpsanlK9_mVJ@monoceros \
--to=ukleinek@kernel.org \
--cc=conor+dt@kernel.org \
--cc=deaner92@yahoo.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®