jcarr
/
linux-firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

linux-firmware: add README 

basic info about how to submit files or patches.

Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
This commit is contained in:
Xose Vazquez Perez 2012-04-22 00:27:14 +02:00 committed by Ben Hutchings
parent 375e9548bf
commit 9b41488827
1 changed files with 38 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
README Normal file
View File

@ -0,0 +1,38 @@
Linux firmware
==============
<http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git>
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
This repository contains all these firmware images which have been
extracted from older drivers, as well various new firmware images which
we were never permitted to include in a GPL'd work, but which we _have_
been permitted to redistribute under separate cover.
To submit firmware to this repository, please send either a git binary
diff or preferably a git pull request to:
David Woodhouse <dwmw2@infradead.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
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
WHENCE file.
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).
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.