From: Ben Hutchings <ben@decadent.org.uk>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: dwmw2@infradead.org,
Christian Lamparter <chunkeey@googlemail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] linux-firmware: add carl9170 firmware
Date: Sat, 14 Jul 2012 22:06:24 +0100 [thread overview]
Message-ID: <1342299984.25597.490.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <5001DBAF.3060605@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
On Sat, 2012-07-14 at 22:50 +0200, Xose Vazquez Perez wrote:
> On 07/14/2012 09:58 PM, Ben Hutchings wrote:
>
> > We need to include full source, not a pointer to it.
>
> What do you mean ?
>
> An entry like that, in the WHENCE file ?
>
> Source: XXXXX
>
> The complete package is about 111 files, but only 42 are the fw :
> http://github.com/chunkeey/carl9170fw
No, I mean the full source for the firmware must accompany the binary in
linux-firmware.
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-07-14 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 18:46 [PATCH] linux-firmware: add carl9170 firmware Xose Vazquez Perez
2012-07-14 19:58 ` Ben Hutchings
2012-07-14 20:50 ` Xose Vazquez Perez
2012-07-14 21:06 ` Ben Hutchings [this message]
[not found] <1342353398-3147-1-git-send-email-xose.vazquez@gmail.com>
[not found] ` <1342666598.11373.97.camel@deadeye.wl.decadent.org.uk>
[not found] ` <1358162875.15692.14.camel@deadeye.wl.decadent.org.uk>
2013-01-15 22:50 ` Xose Vazquez Perez
2013-01-17 21:26 ` Ben Hutchings
2013-01-17 23:52 ` Christian Lamparter
2013-02-18 3:15 ` Ben Hutchings
2013-02-18 14:42 ` Christian Lamparter
-- strict thread matches above, loose matches on Subject: below --
2012-07-14 18:44 Xose Vazquez Perez
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=1342299984.25597.490.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=chunkeey@googlemail.com \
--cc=dwmw2@infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=xose.vazquez@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.