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 <jwboyer@kernel.org>

diff --git a/README.md b/README.md
index 3c73b324749268e2fd72f8bdb8981ef06488b2bc..90d2283ce5f803dead8af331f071c8fddd725f0d 100644 (file)
--- 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