From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>, LKML <linux-kernel@vger.kernel.org>
Cc: linux-firmware@kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH RESEND] firmware: Update information in linux.git about adding firmware
Date: Fri, 17 Apr 2015 18:05:10 +0200 [thread overview]
Message-ID: <55312F36.2000601@gmail.com> (raw)
In-Reply-To: <1428891620.29665.62.camel@decadent.org.uk>
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-
next prev parent reply other threads:[~2015-04-17 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 2:20 [PATCH RESEND] firmware: Update information in linux.git about adding firmware Ben Hutchings
2015-04-17 16:05 ` Xose Vazquez Perez [this message]
2015-05-07 15:49 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2014-08-22 23:38 Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55312F36.2000601@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox