From: Rob Herring <robh+dt@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Adrian Ratiu <adrian.ratiu@collabora.com>,
devicetree@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Neil Armstrong <narmstrong@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Collabora Kernel ML <kernel@collabora.com>
Subject: Re: Rule for bridge yaml dt binding maintainers?
Date: Wed, 22 Apr 2020 15:02:43 -0500 [thread overview]
Message-ID: <CAL_JsqJXa8QxQmLfkCO8_SSsgYm2nTFW1J6wx4bGbZgAy8Sxog@mail.gmail.com> (raw)
In-Reply-To: <20200420175909.GA5810@ravnborg.org>
On Mon, Apr 20, 2020 at 12:59 PM Sam Ravnborg <sam@ravnborg.org> wrote:
>
> Hi Adrian
>
> On Mon, Apr 20, 2020 at 02:19:24PM +0300, Adrian Ratiu wrote:
> > Hello,
> >
> > I got confused while doing the txt -> yaml conversion at [1] and it's still
> > not clear to me who should be added in the "maintainers" field. Clearly not
> > the maintainers as returned by get_maintainer.pl. :)
> >
> > Rob mentioned that "owners" should be manintainers but I also have trouble
> > picking the persons who should be owners / yaml maintainers.
> >
> > Looking at the completed bridge conversions in the latest linux-next, I
> > couldn't find a rule and the majority of bindings are still txt:
> >
> > $ find ./devicetree/bindings/display/bridge/ -name *txt | wc -l
> > 23
> > $ find ./devicetree/bindings/display/bridge/ -name *yaml | wc -l
> > 5
> >
> > So my questions are:
> > 1. Is there a general rule for assigning yaml file owners/maintainers?
> >
> > 2. Is this vagueness specific to the bridge dt bindings only?
> >
> > 3. Who should step up and maintain these bindings? Original/new authors,
> > SoC, bridge, DRM maintainers etc.?
> >
> > It would be useful to have a rule to make it easier to do these conversions.
> > We (Collabora) are considering doing the conversion work.
>
> For the panel conversion I did recently it was simple:
> 1) If listed in MAINTAINERS - use this info
> 2) Otherwise use the person(s) that authored the original .txt file.
> Using git log --follow foo.txt
> 3) In a few cases I may have decided otherwise, but the above covers the
> majority.
Yes.
> I would also be great if you or someone else could:
> - teach get_maintainers about .yaml file listed maintainers
It already does to some extent. IIRC, there's a mode to extract email
addresses from files.
I was hoping that the MAINTAINERS file split happens sometime and we
can just generate a MAINTAINERS file for bindings.
> - teach checkpatch that it is OK to convert .txt to .yaml
Yeah, I should fix my bug.
> - teach checkpatch about some simple yaml validation (maybe)
I don't see checkpatch being able to check much of what comes up in
review. Maybe indentation.
> I am looking forward to the day we have more .yaml files
> than .txt files in Documentation/devicetree/binding/*
700 vs. 3000 currently. It's about 60-70 new bindings and ~100
conversions per cycle. At this point we're review limited I think and
at the current rate, we should be done in 7 years. Yay! :( We need a
faster way.
Rob
next prev parent reply other threads:[~2020-04-22 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:19 Rule for bridge yaml dt binding maintainers? Adrian Ratiu
2020-04-20 17:59 ` Sam Ravnborg
2020-04-22 20:02 ` Rob Herring [this message]
2020-04-22 23:43 ` Joe Perches
2020-04-23 5:22 ` Sam Ravnborg
2020-04-27 5:40 ` [PATCH] get_maintainer: Add email addresses from .yaml files Joe Perches
2020-04-27 5:57 ` Sam Ravnborg
2020-04-27 6:33 ` Joe Perches
2020-04-27 20:04 ` Andrew Morton
2020-04-27 20:26 ` Joe Perches
2020-04-27 20:32 ` Sam Ravnborg
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=CAL_JsqJXa8QxQmLfkCO8_SSsgYm2nTFW1J6wx4bGbZgAy8Sxog@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=a.hajda@samsung.com \
--cc=adrian.ratiu@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).