|author||Ben Hutchings <firstname.lastname@example.org>||2015-04-13 03:20:20 +0100|
|committer||Jonathan Corbet <email@example.com>||2015-05-07 09:48:42 -0600|
firmware: Update information in linux.git about adding firmware
Kyle McMartin joined the linux-firmware maintainers, and we now have an alias <firstname.lastname@example.org> which reaches all of us. Include that instead of the individual addresses. Add some further recommendations that were already included in the README in linux-firmware.git added by Xose Vazquez Perez <email@example.com>. Signed-off-by: Ben Hutchings <firstname.lastname@example.org> Signed-off-by: Jonathan Corbet <email@example.com>
Diffstat (limited to 'firmware')
1 files changed, 12 insertions, 2 deletions
diff --git a/firmware/README.AddingFirmware b/firmware/README.AddingFirmware
index ea78c3a17eec..bcb5f46aff83 100644
@@ -21,15 +21,25 @@ been permitted to redistribute under separate cover.
To submit firmware to that repository, please send either a git binary
diff or preferably a git pull request to:
- David Woodhouse <firstname.lastname@example.org>
- Ben Hutchings <email@example.com>
+and also cc: to related mailing lists.
Your commit should include an update to the WHENCE file clearly
identifying the licence under which the firmware is available, and
that it is redistributable. If the licence is long and involved, it's
permitted to include it in a separate file and refer to it from the
+And if it were possible, a changelog of the firmware itself.
Ideally, your commit should contain a Signed-Off-By: from someone
authoritative on the licensing of the firmware in question (i.e. from
within the company that owns the code).
+Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or
+request. Otherwise your firmware _will never be accepted_.
+Maintainers are really busy, so don't expect a prompt reply.