Re: [PATCH v3] docs: dt: maintainer: Add Devicetree and OF maintainer profile document
Rob Herring <[email protected]> Mon, 20 Jul 2026 15:12:17 -0500
| Newsgroups | org.kernel.vger.workflows,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAL_JsqKkxVTVE=o-uar=JEVvqw9NhBAQcBrJ0ukf+RBXCwFZJA@mail.gmail.com> |
On Mon, Jul 20, 2026 at 1:40=E2=80=AFPM Krzysztof Kozlowski <[email protected]> wrote: > > Document how Devicetree and Open Firmware maintainers handle their > subsystem, especially focusing on two caveats: > > Devicetree subsystem handles patches with a minor difference comparing > to other subsystems: while DT maintainers pick up OF code, they only > provide review of DT bindings without applying these. > > All three DT bindings maintainers rely currently on Patchwork and due to > enormous amount of emails per day, regardless how much DT maintainers > try, they cannot read all the emails. > > Cc: Rob Herring <[email protected]> > Cc: Conor Dooley <[email protected]> > Cc: Saravana Kannan <[email protected]> > Cc: [email protected] > Signed-off-by: Krzysztof Kozlowski <[email protected]> > > --- > > I expect patch to be picked up by Rob, after review. > > Changes in v3: > 1. Add also F: entry > > Changes in v2: > 1. Correct typos and trailing white spaces. > 2. Fix order of P: after C: in maintainers. > --- > .../process/maintainer-devicetree.rst | 70 +++++++++++++++++++ > MAINTAINERS | 3 + > 2 files changed, 73 insertions(+) > create mode 100644 Documentation/process/maintainer-devicetree.rst > > diff --git a/Documentation/process/maintainer-devicetree.rst b/Documentat= ion/process/maintainer-devicetree.rst > new file mode 100644 > index 000000000000..d8ffe752bf5d > --- /dev/null > +++ b/Documentation/process/maintainer-devicetree.rst > @@ -0,0 +1,70 @@ > +.. SPDX-License-Identifier: GPL-2.0 > + > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +Devicetree and Open Firmware Subsystem > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > + > +Other Process Documents > +----------------------- > + > +Please see the documents in Documentation/devicetree/bindings/ for infor= mation > +on how to write proper Devicetree bindings and how to submit patches. > + > +Patch Review and Handling > +------------------------- > + > +Patches handled by Devicetree maintainers are processed differently depe= nding > +on the patch type: > + > +1. Core OF driver code, e.g. drivers/of/: > + patches are reviewed and applied by DT maintainers. > + > +2. Devicetree bindings: > + patches are reviewed by DT maintainers but, except in certain cases, = should > + be applied by subsystem maintainers. See also *For kernel maintainer= s* in > + Documentation/devicetree/bindings/submitting-patches.rst. I would reword: patches are reviewed by DT maintainers, but should be applied by subsystem maintainers except in certain cases. > + > +3. DTS and drivers: > + DT maintainers might provide comments, but review is generally not ex= pected. For DTS, we expect to pass schema checks or at least not add new warnings. I can address these 2 when applying. Rob