From: Guenter Roeck <linux@roeck-us.net>
To: Frank Li <Frank.li@nxp.com>
Cc: Mark Brown <broonie@kernel.org>, Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
"open list:HARDWARE MONITORING" <linux-hwmon@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH v2 1/1] dt-bindings: hwmon/regulator: Convert ltc2978.txt to yaml
Date: Mon, 19 Aug 2024 14:37:00 -0700 [thread overview]
Message-ID: <e63f6e5b-09a8-400f-8425-8dac4284fc9d@roeck-us.net> (raw)
In-Reply-To: <ZsOfeimD94+mh5gt@lizhi-Precision-Tower-5810>
On Mon, Aug 19, 2024 at 03:39:38PM -0400, Frank Li wrote:
> On Mon, Aug 19, 2024 at 08:11:46PM +0100, Mark Brown wrote:
> > On Mon, Aug 19, 2024 at 03:06:51PM -0400, Frank Li wrote:
> >
> > > change from v1 to v2
> > > - maintainer change to Mark Brown <broonie@kernel.org> (regulator maintainer)
> >
> > I also shouldn't be the maintainer for this specific binding, it should
> > be someone with knowledge of the devices. This is a requirement imposed
> > by the DT people, I'd be happy to just not list a specific maintainer.
>
> I remember 'maintainer' is required property for yaml.
> Look like Guenter Roeck contribute many code for this driver.
>
Yes, but I do not maintain code or documentation outside the hardware
monitoring or watchdog subsystems. You want this file attached to the
regulator subsystem, so you'll have to find a maintainer from that
subsystem or sign up to maintain it yourself.
Guenter
next prev parent reply other threads:[~2024-08-19 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 19:06 Frank Li
2024-08-19 19:11 ` Mark Brown
2024-08-19 19:39 ` Frank Li
2024-08-19 21:37 ` Guenter Roeck [this message]
2024-08-19 21:45 ` Frank Li
2024-08-25 23:03 ` Guenter Roeck
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=e63f6e5b-09a8-400f-8425-8dac4284fc9d@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Frank.li@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@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®