From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Christian Lamparter <chunkeey@googlemail.com>,
Lauri Kasanen <cand@gmx.com>, Kalle Valo <kvalo@codeaurora.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev@vger.kernel.org,
Linux Firmware Maintainers <linux-firmware@kernel.org>
Subject: Re: [PATCH v2] carl9170: Clarify kconfig text
Date: Mon, 18 Apr 2016 18:47:44 +0200 [thread overview]
Message-ID: <c17f2f12-1c94-6b19-c918-0a6a9ee401ca@gmail.com> (raw)
Christian Lamparter wrote:
> Sure, but this could be a different patch then. I think Intel devices
> (iwlwifi, iwlegacy and ipw2x00) have a similar text about "download
> firmware from this device from our homepage here" too. So if we want,
> we can remove them altogether?
linux-firmware.git does not contain firmware for all drivers. _At least_
zd1211rw [1], atmel [2] and ipw2x00 [3] are out of the tree.
[1] http://sf.net/projects/zd1211/files/
[2] http://web.archive.org/web/20121016132320/http://at76c503a.berlios.de/fw_dl.html
[3] http://ipw2100.sf.net/firmware.php http://ipw2200.sf.net/firmware.php
next reply other threads:[~2016-04-18 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 16:47 Xose Vazquez Perez [this message]
2016-04-18 17:10 ` [PATCH v2] carl9170: Clarify kconfig text Christian Lamparter
-- strict thread matches above, loose matches on Subject: below --
2016-04-16 8:33 [PATCH] " Lauri Kasanen
[not found] ` <1466768.7dLuLFSDol@debian64>
2016-04-16 14:18 ` [PATCH v2] " Lauri Kasanen
2016-04-16 15:32 ` Christian Lamparter
[not found] ` <20160416171856.1769c0e16bcc75372407e06f-KK0ffGbhmjU@public.gmane.org>
2016-04-18 15:45 ` Kalle Valo
[not found] ` <87shyiyl8a.fsf-5ukZ45wKbUHoml4zekdYB16hYfS7NtTn@public.gmane.org>
2016-04-18 16:20 ` Christian Lamparter
2016-04-18 16:42 ` Kalle Valo
[not found] ` <87r3e2kgwy.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2016-04-18 17:07 ` Christian Lamparter
2016-04-20 7:59 ` Kalle Valo
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=c17f2f12-1c94-6b19-c918-0a6a9ee401ca@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=cand@gmx.com \
--cc=chunkeey@googlemail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).