From: Mark Brown <broonie@kernel.org>
To: "André Apitzsch" <git@apitzsch.eu>
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] dt-bindings: regulator: Convert ti,tps65133 to YAML
Date: Fri, 22 Dec 2023 14:49:42 +0000 [thread overview]
Message-ID: <b67eba2a-b07a-4076-92bb-07bd0faf338e@sirena.org.uk> (raw)
In-Reply-To: <951a01b5da3061e1ac1d396ba7f6629e3a0e9a1e.camel@apitzsch.eu>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Fri, Dec 22, 2023 at 08:50:14AM +0100, André Apitzsch wrote:
> Am Sonntag, dem 17.12.2023 um 08:24 -0600 schrieb Rob Herring:
> > On Sun, 17 Dec 2023 14:21:39 +0100, André Apitzsch wrote:
> > dtschema/dtc warnings/errors:
> > /builds/robherring/dt-review-
> > ci/linux/Documentation/devicetree/bindings/regulator/ti,tps65132.yaml
> > : 'maintainers' is a required property
> > hint: Metaschema for devicetree binding documentation
> > from schema $id:
> > http://devicetree.org/meta-schemas/base.yaml#
> I haven't add a maintainer, yet, as the driver for tps65132 doesn't
> list one.
> Who is willing to be listed as maintainer for this device or who can be
> asked to become a maintainer for tps65132?
You could just put the list in as a fallback I guess?
The requirement for DT maintainer does seem to in conflict with the push
to convert things when people are doing incidental work on the driver...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-12-22 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 13:21 André Apitzsch
2023-12-17 14:24 ` Rob Herring
2023-12-22 7:50 ` André Apitzsch
2023-12-22 14:49 ` Mark Brown [this message]
2023-12-23 14:17 ` Krzysztof Kozlowski
2023-12-28 17:40 ` Mark Brown
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=b67eba2a-b07a-4076-92bb-07bd0faf338e@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@apitzsch.eu \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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®