.../process/maintainer-devicetree.rst | 70 +++++++++++++++++++ MAINTAINERS | 3 + 2 files changed, 73 insertions(+) create mode 100644 Documentation/process/maintainer-devicetree.rst
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 <robh@kernel.org>
Cc: Conor Dooley <conor+dt@kernel.org>
Cc: Saravana Kannan <saravanak@kernel.org>
Cc: devicetree@vger.kernel.org
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
---
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/Documentation/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
+
+======================================
+Devicetree and Open Firmware Subsystem
+======================================
+
+Other Process Documents
+-----------------------
+
+Please see the documents in Documentation/devicetree/bindings/ for information
+on how to write proper Devicetree bindings and how to submit patches.
+
+Patch Review and Handling
+-------------------------
+
+Patches handled by Devicetree maintainers are processed differently depending
+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 maintainers* in
+ Documentation/devicetree/bindings/submitting-patches.rst.
+
+3. DTS and drivers:
+ DT maintainers might provide comments, but review is generally not expected.
+
+Patchwork
+~~~~~~~~~
+
+Devicetree maintainers review patches using Patchwork, so the current status of
+a patch can be checked there. For typical driver submissions, Patchwork
+receives the entire patch set, but only a few patches are usually Devicetree
+bindings that are reviewed by DT maintainers.
+
+Explanation of Patchwork statuses:
+
+ - **New**: Not yet processed by the automation toolset.
+ - **Needs ACK**: Waiting for review by DT maintainers.
+ - **Handled Elsewhere**: Non-DT patch; not being reviewed here.
+ - **RFC**: Patch was likely ignored because it was an incomplete RFC.
+ - **Changes Requested**: Patch was reviewed and DT maintainers expect changes.
+ - **Accepted**: Patch was reviewed and applied by DT maintainers to their tree.
+ - **Not Applicable**: Patch was reviewed and is likely in good shape, with a
+ *Reviewed-by* or *Acked-by* tag provided, but DT maintainers expect someone
+ else to apply it.
+
+Patch Re-review and Pinging
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Due to the high volume of email traffic, Devicetree maintainers do not read
+every email they receive and instead rely on Patchwork during the review
+process. They also often skip patches that have already been reviewed.
+
+As a result, maintainers might miss:
+
+1. Questions about already reviewed patches.
+2. Pings, for example when a patch has been reviewed by DT maintainers but has
+ not been picked up by subsystem maintainers.
+
+Such cases can be addressed by:
+
+1. Pinging DT maintainers on the IRC channel.
+2. Dropping the DT maintainer’s *Acked-by* or *Reviewed-by* tag when sending a new
+ version of the patch set, together with an explanation in the patch
+ changelog describing why the tag was removed and what is expected from DT
+ maintainers.
+
diff --git a/MAINTAINERS b/MAINTAINERS
index 0b6b9e6b3900..be6aa5d174c5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20285,6 +20285,7 @@ S: Maintained
Q: http://patchwork.kernel.org/project/devicetree/list/
W: http://www.devicetree.org/
C: irc://irc.libera.chat/devicetree
+P: Documentation/process/maintainer-devicetree.rst
T: git git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
F: Documentation/ABI/testing/sysfs-firmware-ofw
F: drivers/of/
@@ -20306,8 +20307,10 @@ L: devicetree@vger.kernel.org
S: Maintained
Q: http://patchwork.kernel.org/project/devicetree/list/
C: irc://irc.libera.chat/devicetree
+P: Documentation/process/maintainer-devicetree.rst
T: git git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
F: Documentation/devicetree/
+F: Documentation/process/maintainer-devicetree.rst
F: arch/*/boot/dts/
F: include/dt-bindings/
--
2.53.0
On Mon, Jul 20, 2026 at 1:40 PM Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> 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 <robh@kernel.org> > Cc: Conor Dooley <conor+dt@kernel.org> > Cc: Saravana Kannan <saravanak@kernel.org> > Cc: devicetree@vger.kernel.org > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> > > --- > > 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/Documentation/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 > + > +====================================== > +Devicetree and Open Firmware Subsystem > +====================================== > + > +Other Process Documents > +----------------------- > + > +Please see the documents in Documentation/devicetree/bindings/ for information > +on how to write proper Devicetree bindings and how to submit patches. > + > +Patch Review and Handling > +------------------------- > + > +Patches handled by Devicetree maintainers are processed differently depending > +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 maintainers* 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 expected. For DTS, we expect to pass schema checks or at least not add new warnings. I can address these 2 when applying. Rob
On 20/07/2026 22:12, Rob Herring wrote: > On Mon, Jul 20, 2026 at 1:40 PM Krzysztof Kozlowski > <krzysztof.kozlowski@oss.qualcomm.com> 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 <robh@kernel.org> >> Cc: Conor Dooley <conor+dt@kernel.org> >> Cc: Saravana Kannan <saravanak@kernel.org> >> Cc: devicetree@vger.kernel.org >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> >> >> --- >> >> 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/Documentation/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 >> + >> +====================================== >> +Devicetree and Open Firmware Subsystem >> +====================================== >> + >> +Other Process Documents >> +----------------------- >> + >> +Please see the documents in Documentation/devicetree/bindings/ for information >> +on how to write proper Devicetree bindings and how to submit patches. >> + >> +Patch Review and Handling >> +------------------------- >> + >> +Patches handled by Devicetree maintainers are processed differently depending >> +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 maintainers* 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 expected. > > For DTS, we expect to pass schema checks or at least not add new warnings. > > I can address these 2 when applying. > I'll make a v4, no problem. Best regards, Krzysztof
On Mon, Jul 20, 2026 at 03:12:17PM -0500, Rob Herring wrote: > On Mon, Jul 20, 2026 at 1:40 PM Krzysztof Kozlowski > <krzysztof.kozlowski@oss.qualcomm.com> 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 <robh@kernel.org> > > Cc: Conor Dooley <conor+dt@kernel.org> > > Cc: Saravana Kannan <saravanak@kernel.org> > > Cc: devicetree@vger.kernel.org > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> > > > > --- > > > > 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/Documentation/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 > > + > > +====================================== > > +Devicetree and Open Firmware Subsystem > > +====================================== > > + > > +Other Process Documents > > +----------------------- > > + > > +Please see the documents in Documentation/devicetree/bindings/ for information > > +on how to write proper Devicetree bindings and how to submit patches. > > + > > +Patch Review and Handling > > +------------------------- > > + > > +Patches handled by Devicetree maintainers are processed differently depending > > +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 maintainers* 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. It would be wonderful if provide a few sample *certain* cases. Anyways, nice document. Reviewed-by: Frank Li <Frank.Li@nxp.com> > > > + > > +3. DTS and drivers: > > + DT maintainers might provide comments, but review is generally not expected. > > For DTS, we expect to pass schema checks or at least not add new warnings. > > I can address these 2 when applying. > > Rob
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> writes: > 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 <robh@kernel.org> > Cc: Conor Dooley <conor+dt@kernel.org> > Cc: Saravana Kannan <saravanak@kernel.org> > Cc: devicetree@vger.kernel.org > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> > > --- > > 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 You'll need to add this new file to index.rst as well. Thanks, jon
On 20/07/2026 21:19, Jonathan Corbet wrote: >> 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 > > You'll need to add this new file to index.rst as well. Hm, where? In docs/process/index.rst? None of the other maintainer profiles are mentioned there. Best regards, Krzysztof
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> writes: > On 20/07/2026 21:19, Jonathan Corbet wrote: >>> 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 >> >> You'll need to add this new file to index.rst as well. > > Hm, where? In docs/process/index.rst? None of the other maintainer > profiles are mentioned there. Sigh...I stand corrected. I'd forgotten that we merged the maintainers-profile-toc Sphinx magic that picks them all up from the MAINTAINERS file entries. Sorry for the noise, jon
© 2016 - 2026 Red Hat, Inc.