linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: fariyaf@gmail.com, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Fwd: Submission of firmware for driver RSI
Date: Fri, 04 Apr 2014 18:14:06 +0200	[thread overview]
Message-ID: <533EDA4E.9020308@gmail.com> (raw)

Fariya wrote:

> I would like to submit the RSI firmware to the linux-firmware git. Can
> anyone point me to the procedure for f/w submission? Can I submit the
> f/w onto this mailing list?

https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/README
is your friend:

--cut--

	Linux firmware
	==============

  <http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git>

  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 <dwmw2@infradead.org>
      Ben Hutchings <ben@decadent.org.uk>
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.
--theend--

             reply	other threads:[~2014-04-04 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 16:14 Xose Vazquez Perez [this message]
2014-04-16  2:18 ` Fwd: Submission of firmware for driver RSI Fariya
2014-04-16  6:16   ` Xose Vazquez Perez
     [not found] <CAG+h2qjs9WanwFjE7=kAhV2Z4ObaQ7pGqH_+5w-pqz9JED_u=A@mail.gmail.com>
2014-04-04  7:20 ` Fariya
2014-04-04 10:25   ` Arend van Spriel

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=533EDA4E.9020308@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=fariyaf@gmail.com \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).