From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: ksummit@lists.linux.dev
Subject: [MAINTAINERS SUMMIT] State of dt-bindings and DT source files, and invitation request
Date: Tue, 10 Sep 2024 13:52:52 +0300 [thread overview]
Message-ID: <972ed553-c917-41d1-be6e-b8a3ab90b66a@arinc9.com> (raw)
Hello.
I maintain the MediaTek DSA subdriver and some devicetree bindings and
source files for MediaTek hardware.
I am especially interested in the best practices of maintaining dt-bindings
and DT source files.
There's this false impression with some maintainers that, as the
dt-bindings and the DT source files are being hosted on the Linux
repository, Linux drivers have influence over the design of bindings or
fixing DT source files that did not comply with the bindings.
I'd be very interested to be involved in or kick start the efforts to take
dt-bindings and DT source files out of the Linux repository into its own,
separate repository. I believe, this would be a great step in addressing
all the project-dependent bindings of Linux, U-Boot, OpenWrt, and all other
projects, to have a single, unified repository to describe all the hardware
that exists in the world. I am already working towards this goal by
improving the dt-bindings and DT source files on the Linux repository
whenever I can.
I must be quite late to make a topic suggestion but I'd be very happy to be
able to attend to the maintainers summit. I've already registered for the
Linux Plumbers Conference 2024.
Arınç
next reply other threads:[~2024-09-10 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 10:52 Arınç ÜNAL [this message]
2024-09-10 15:46 ` Rob Herring
2024-09-10 21:53 ` Conor Dooley
2024-09-12 13:01 ` Arınç ÜNAL
2024-09-12 15:12 ` Mark Brown
2024-09-12 17:05 ` Conor Dooley
2024-09-13 5:50 ` Arınç ÜNAL
2024-09-12 12:57 ` Arınç ÜNAL
2024-09-13 8:08 ` David Woodhouse
2024-09-13 15:38 ` Arınç ÜNAL
2024-09-13 16:13 ` Conor Dooley
2024-09-14 13:49 ` Arınç ÜNAL
2024-09-19 14:55 ` Rob Herring
2024-09-20 9:53 ` Arınç ÜNAL
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=972ed553-c917-41d1-be6e-b8a3ab90b66a@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=ksummit@lists.linux.dev \
/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