From 9b414888272b6b8107f3810136553d7013e0dbe1 Mon Sep 17 00:00:00 2001 From: Xose Vazquez Perez Date: Sun, 22 Apr 2012 00:27:14 +0200 Subject: [PATCH] linux-firmware: add README basic info about how to submit files or patches. Signed-off-by: Xose Vazquez Perez Signed-off-by: Ben Hutchings --- README | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 README diff --git a/README b/README new file mode 100644 index 0000000..0ed6d79 --- /dev/null +++ b/README @@ -0,0 +1,38 @@ + + Linux firmware + ============== + + + + 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 + Ben Hutchings +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.