Mirrors/u-boot
1
0
Fork 0
mirror of https://source.denx.de/u-boot/u-boot.git synced 2026-06-13 15:03:58 +03:00
Code Issues Packages Projects Releases Wiki Activity

doc: develop: process: Explain when/how Custodians may edit patches

Browse Source 
As seen with commit d503633a36 ("Revert "doc: board: starfive: update
jh7110 common description""), it has not always been clear what is and
isn't allowed by custodians, and what the expectations are. To prevent
further unintentional conflicts, document the limited cases where
custodians are allowed to modify patches directly, and how to do that.

Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
This commit is contained in:
Tom Rini
2026-01-20 14:11:45 -06:00
committed by Heinrich Schuchardt
parent 78e100db5b
commit 7db33677c2
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/develop/process.rst
View File

@@ -144,6 +144,12 @@ feedback to the submitter of a patch about what is going on:
feels it has been too long since posting their patch and not
received any feedback, it is OK to follow-up and ask.
* A custodian may make changes suggested by :doc:`checkpatch.pl
<checkpatch>`. They must also in turn amend the commit message noting
their change, for example ``[trini: Fix typos]``, and add their own
:ref:`Signed-off-by <dco>` tag. All other changes must be handled by
another iteration of the patch, or follow-up patch.
* If the patch itself can still be applied to the tree. The custodian
is expected to put in a "best effort" if a patch does not apply
cleanly, but can be made to apply still. It is up to the custodian