github-mirror/linux
1
0
Fork 0
mirror of https://github.com/torvalds/linux.git synced 2026-09-23 13:14:02 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity Graph

docs: submitting-patches: Fix section structure around DCO

Browse Source 
Commit 5903019b2a ("Documentation/SubmittingPatches: convert it to
ReST markup") made "DCO 1.1" a subsection under the section "Sign your
work - ...".  However, the DCO text is meant to be referenced in the
section.

Furthermore, in HTML and PDF docs, paragraphs following the DCO:

    then you just add a line saying:

        Signed-off-by: [...]

    [...]
    as it was propagated to the maintainers and ultimately to Linus, with
    the first SoB entry signalling primary authorship of a single author.

appear to belong to the DCO, rather than to "Sign your work - ..."
where it should.

In reST (and other documentation tools), once you start a subsection
under a section, there is no way to go back to the section.

Fix the section structure by making the DCO a literal block, with
indent changes made in commit 5903019b2a reverted.

While at it, fix the same issue at "Reviewer's statement of
oversight".

Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <5f320260-5cb0-42cc-949a-c92404124618@gmail.com>
This commit is contained in:
Akira Yokosawa 2026-07-02 19:44:15 +09:00 committed by Jonathan Corbet
parent e6f09a8911
commit 83f71fbc66
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Documentation/process/submitting-patches.rst
View File

@ -404,12 +404,11 @@ patches that are being emailed around.
The sign-off is a simple line at the end of the explanation for the The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to patch, which certifies that you wrote it or otherwise have the right to
pass it on as an open-source patch. The rules are pretty simple: if you pass it on as an open-source patch. The rules are pretty simple: if you
can certify the below: can certify the below::
Developer's Certificate of Origin 1.1 Developer's Certificate of Origin 1.1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
By making a contribution to this project, I certify that: By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I (a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license have the right to submit it under the open source license
@ -554,12 +553,11 @@ some testing has been performed, provides a means to locate testers for
future patches, and ensures credit for the testers. future patches, and ensures credit for the testers.
Reviewed-by:, instead, indicates that the patch has been reviewed and found Reviewed-by:, instead, indicates that the patch has been reviewed and found
acceptable according to the Reviewer's Statement: acceptable according to the Reviewer's Statement::
Reviewer's statement of oversight Reviewer's statement of oversight
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
By offering my Reviewed-by: tag, I state that: By offering my Reviewed-by: tag, I state that:
(a) I have carried out a technical review of this patch to (a) I have carried out a technical review of this patch to
evaluate its appropriateness and readiness for inclusion into evaluate its appropriateness and readiness for inclusion into