[PATCH RESEND] firmware: Update information in linux.git about adding firmware

[PATCH RESEND] firmware: Update information in linux.git about adding firmware

[Ben Hutchings]

[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]

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>
---
 firmware/README.AddingFirmware | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/firmware/README.AddingFirmware b/firmware/README.AddingFirmware
index ea78c3a..bcb5f46 100644
--- a/firmware/README.AddingFirmware
+++ b/firmware/README.AddingFirmware
@@ -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 <dwmw2@infradead.org>
-      Ben Hutchings <ben@decadent.org.uk>
+      linux-firmware@kernel.org
+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.



-- 
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
                                                           - Albert Einstein

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

Re: [PATCH RESEND] firmware: Update information in linux.git about adding firmware

[Xose Vazquez Perez]

On 04/13/2015 04:20 AM, Ben Hutchings wrote:
> 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>
> ---
>  firmware/README.AddingFirmware | 14 ++++++++++++--
>  1 file changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/firmware/README.AddingFirmware b/firmware/README.AddingFirmware
> index ea78c3a..bcb5f46 100644
> --- a/firmware/README.AddingFirmware
> +++ b/firmware/README.AddingFirmware
> @@ -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 <dwmw2@infradead.org>
> -      Ben Hutchings <ben@decadent.org.uk>
> +      linux-firmware@kernel.org
> +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.
> 
> 
> 

Hi Jonathan,

Could you take this patch?

-thanks-

Re: [PATCH RESEND] firmware: Update information in linux.git about adding firmware

[Jonathan Corbet]

On Fri, 17 Apr 2015 18:05:10 +0200
Xose Vazquez Perez <xose.vazquez@gmail.com> wrote:

> 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

[PATCH RESEND] firmware: Update information in linux.git about adding firmware

[Ben Hutchings]

[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]

Kyle McMartin recently 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>
---
 firmware/README.AddingFirmware | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/firmware/README.AddingFirmware b/firmware/README.AddingFirmware
index ea78c3a..bcb5f46 100644
--- a/firmware/README.AddingFirmware
+++ b/firmware/README.AddingFirmware
@@ -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 <dwmw2@infradead.org>
-      Ben Hutchings <ben@decadent.org.uk>
+      linux-firmware@kernel.org
+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.


-- 
Ben Hutchings
Lowery's Law:
             If it jams, force it. If it breaks, it needed replacing anyway.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]