The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Akiyoshi Kurita <weibu@redadmin.org>,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH -next] docs: submitting-patches: Fix section structure around DCO
Date: Fri, 10 Jul 2026 13:46:40 -0600	[thread overview]
Message-ID: <87mrvyk4pr.fsf@trenco.lwn.net> (raw)
In-Reply-To: <5f320260-5cb0-42cc-949a-c92404124618@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

> Commit 5903019b2a5e ("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 5903019b2a5e reverted.
>
> While at it, fix the same issue at "Reviewer's statement of
> oversight".
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> ---
>  Documentation/process/submitting-patches.rst | 14 ++++++--------
>  1 file changed, 6 insertions(+), 8 deletions(-)

Applied, thanks.

jon

      parent reply	other threads:[~2026-07-10 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 10:44 [PATCH -next] docs: submitting-patches: Fix section structure around DCO Akira Yokosawa
2026-07-08 21:04 ` Randy Dunlap
2026-07-09 10:34   ` weibu
2026-07-10 19:46 ` Jonathan Corbet [this message]

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=87mrvyk4pr.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=weibu@redadmin.org \
    /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