Skip to contentSkip to conversation

firmware: Update information in linux.git about adding firmware

PATCH RESEND Applied Ben Hutchings 3 participants 3 messages Apr 13, 2015 – May 7, 2015

lore
Share & tools
lore
#0 lore raw

PATCH RESEND 1/1 firmware: Update information in linux.git about adding firmware

Kyle McMartin joined the linux-firmware maintainers, and we now have an alias <[email protected]> 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 protected]>.

---
 firmware/README.AddingFirmware | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)
firmware/README.AddingFirmware +12 -2
index ea78c3a..bcb5f46 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 <[email protected]>
-      Ben Hutchings <[email protected]>
+      [email protected]
+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.
Signature · 3 lines
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
                                                           - Albert Einstein
#1 lore raw
Quoted 38 lines · Ben Hutchings

Kyle McMartin joined the linux-firmware maintainers, and we now have an alias <[email protected]> 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 protected]>.

---
 firmware/README.AddingFirmware | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)
firmware/README.AddingFirmware +3 -2
index ea78c3a..bcb5f46 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 <[email protected]>
-      Ben Hutchings <[email protected]>
+      [email protected]
+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

firmware/README.AddingFirmware been permitted to redistribute under separate cover. · line 45

Quoted 10 lines
firmware/README.AddingFirmware +9 -0
 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.

Hi Jonathan,

Could you take this patch?

-thanks-

#2 lore raw
Quoted 1 line · On Fri, 17 Apr 2015 18:05:10 +0200 Xose Vazquez Perez <[email protected]>…

Could you take this patch?

Applied to the docs tree. Thanks for calling my attention to it; it wasn't addressed to me and I would have missed it otherwise.

jon