From: Andrew Morton <akpm@digeo.com>
To: jt@hpl.hp.com
Cc: jt@bougret.hpl.hp.com, jgarzik@pobox.com,
linux-kernel@vger.kernel.org, hermes@gibson.dropbear.id.au,
breed@almaden.ibm.com, achirica@ttd.net, jkmaline@cc.hut.fi
Subject: Re: airo and firmware upload (was Re: 2.6 must-fix list, v3)
Date: Wed, 14 May 2003 16:38:26 -0700 [thread overview]
Message-ID: <20030514163826.6459cd93.akpm@digeo.com> (raw)
In-Reply-To: <20030514233235.GA11581@bougret.hpl.hp.com>
Jean Tourrilhes <jt@bougret.hpl.hp.com> wrote:
>
> firmwares blobs
well for the purposes of tracking 2.6 activities I'll separate this issue
of firmware access policy out from drivers/net/wireless/.
yeah, it would be nice if the core kernel provided a "give me my firmware"
API or something.
next prev parent reply other threads:[~2003-05-14 23:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 21:12 2.6 must-fix list, v3 Jean Tourrilhes
2003-05-14 22:06 ` airo and firmware upload (was Re: 2.6 must-fix list, v3) Jeff Garzik
2003-05-14 23:32 ` Jean Tourrilhes
2003-05-14 23:38 ` Andrew Morton [this message]
2003-05-15 1:04 ` David Gibson
2003-05-16 7:27 ` Manuel Estrada Sainz
2003-05-14 23:43 ` Dave Jones
2003-05-14 23:53 ` Jeff Garzik
2003-05-15 0:59 ` Jouni Malinen
2003-05-15 2:20 ` Jean Tourrilhes
2003-05-15 6:16 ` James Morris
2003-05-15 1:02 ` Jean Tourrilhes
2003-05-15 4:21 ` CryptoAPI and WEP/stream ciphers (was: airo and firmware upload) Jouni Malinen
2003-05-15 6:04 ` James Morris
2003-05-15 0:55 ` airo and firmware upload (was Re: 2.6 must-fix list, v3) Jean Tourrilhes
2003-05-15 7:13 ` Greg KH
2003-05-15 17:24 ` Jean Tourrilhes
2003-05-15 17:46 ` Greg KH
2003-05-15 19:55 ` Jean Tourrilhes
2003-05-15 20:10 ` Greg KH
2003-05-17 16:58 ` 2.6 must-fix list, v3 Pavel Machek
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=20030514163826.6459cd93.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=achirica@ttd.net \
--cc=breed@almaden.ibm.com \
--cc=hermes@gibson.dropbear.id.au \
--cc=jgarzik@pobox.com \
--cc=jkmaline@cc.hut.fi \
--cc=jt@bougret.hpl.hp.com \
--cc=jt@hpl.hp.com \
--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
all inboxes | Powered by JetHome®