From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] doc: develop/process: Clarify name usage in the Signed-off-by line
Date: Tue, 3 Feb 2026 13:16:20 -0600 [thread overview]
Message-ID: <20260203191620.1476575-1-trini@konsulko.com> (raw)
Long ago we took the Linux Kernel documentation about adding a
Signed-off-by line and adjusted it slightly for how we organized things.
In 2003 Linus clarified the intent and then re-worded what the name
portion of the Signed-off-by line can be. Mirror that change here.
Link: https://git.kernel.org/torvalds/c/d4563201f33a
Signed-off-by: Tom Rini <trini@konsulko.com>
---
doc/develop/process.rst | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/doc/develop/process.rst b/doc/develop/process.rst
index fd81d9c5ebd4..3c783ed5a0e9 100644
--- a/doc/develop/process.rst
+++ b/doc/develop/process.rst
@@ -139,8 +139,7 @@ document.
message by which the signer certifies that they were involved in the development
of the patch and that they accept the `Developer Certificate of Origin
<https://developercertificate.org/>`_. Following this and adding a
- ``Signed-off-by:`` line that contains the developer's name and email address
- is required.
+ ``Signed-off-by:`` line using a known identity and email address is required.
* Please note that in U-Boot, we do not add a ``Signed-off-by`` tag if we
just pass on a patch without any changes.
--
2.43.0
next reply other threads:[~2026-02-03 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 19:16 Tom Rini [this message]
2026-02-03 19:58 ` [PATCH] doc: develop/process: Clarify name usage in the Signed-off-by line Quentin Schulz
2026-02-03 20:03 ` Tom Rini
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=20260203191620.1476575-1-trini@konsulko.com \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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