[PATCH] linux-firmware: add README

From: Xose Vazquez Perez
Date: Sat Apr 21 2012 - 18:27:24 EST

basic info about how to submit files or patches.

Signed-off-by: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
README | 38 ++++++++++++++++++++++++++++++++++++++
1 files changed, 38 insertions(+), 0 deletions(-)
create mode 100644 README

diff --git a/README b/README
new file mode 100644
index 0000000..36c47b2
--- /dev/null
+++ b/README
@@ -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@xxxxxxxxxxxxx>
+ Ben Hutchings <ben@xxxxxxxxxxxxxxx>
+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).
+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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/