firmware: Update information in linux.git about adding firmware

Kyle McMartin joined the linux-firmware maintainers, and we now
have an alias <linux-firmware@kernel.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
<xose.vazquez@gmail.com>.

Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Ben Hutchings 2015-04-13 03:20:20 +01:00 committed by Jonathan Corbet
parent e3aa205aa1
commit de88d8becb
1 changed files with 12 additions and 2 deletions

View File

@ -21,15 +21,25 @@ been permitted to redistribute under separate cover.
To submit firmware to that repository, please send either a git binary To submit firmware to that repository, please send either a git binary
diff or preferably a git pull request to: diff or preferably a git pull request to:
David Woodhouse <dwmw2@infradead.org> linux-firmware@kernel.org
Ben Hutchings <ben@decadent.org.uk> and also cc: to related mailing lists.
Your commit should include an update to the WHENCE file clearly Your commit should include an update to the WHENCE file clearly
identifying the licence under which the firmware is available, and identifying the licence under which the firmware is available, and
that it is redistributable. If the licence is long and involved, it's 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 permitted to include it in a separate file and refer to it from the
WHENCE file. WHENCE file.
And if it were possible, a changelog of the firmware itself.
Ideally, your commit should contain a Signed-Off-By: from someone Ideally, your commit should contain a Signed-Off-By: from someone
authoritative on the licensing of the firmware in question (i.e. from authoritative on the licensing of the firmware in question (i.e. from
within the company that owns the code). within the company that owns the code).
WARNING:
=======
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.