On 04/13/2015 04:20 AM, Ben Hutchings wrote:
> Kyle McMartin joined the linux-firmware maintainers, and we now
> have an alias <linux-firmw...@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.vazq...@gmail.com>.
> 
> Signed-off-by: Ben Hutchings <b...@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 <dw...@infradead.org>
> -      Ben Hutchings <b...@decadent.org.uk>
> +      linux-firmw...@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-
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to