From: Josh Boyer Date: Mon, 25 Aug 2025 17:37:33 +0000 (-0400) Subject: Update README.md to clarify S-o-b requirements X-Git-Tag: 20250917~24^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3b7a8ca912ab84d4b93d5a6a8c009edefd690bb7;p=thirdparty%2Flinux-firmware.git Update README.md to clarify S-o-b requirements Corporate accounts can be difficult to use for contributions in some cases. Clarify how to approach this situation. Signed-off-by: Josh Boyer --- diff --git a/README.md b/README.md index 3c73b324..90d2283c 100644 --- a/README.md +++ b/README.md @@ -16,6 +16,21 @@ To submit firmware to this repository, please do one of the following: * send a git binary diff to `linux-firmware@kernel.org` * send a git pull request to: `linux-firmware@kernel.org` +### Signed-off-by requirement + +All commits must include a `Signed-off-by` line to track the provenance of the +firmware. This signature must be from someone with authority over the licensing +of the firmware, typically someone from within the company that owns or +controls the firmware. The `Signed-off-by` line serves as an attestation that +the contributor has the right to submit the firmware under the specified +license terms and that it can be redistributed according to those terms. + +At times, a contributor may work at a location that makes it difficult to +submit patches or MRs from their offical company accounts. In this case, +the `Signed-off-by` line in the commit should still be via the company +address, but the submitter can use a personal address with the company address +on CC for the MR or patch contribution. + ## Quality If your commit adds new firmware, it must update the `WHENCE` file to