From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Arkadiusz Miskiewicz <arekm@pld-linux.org>,
Andrew Morton <akpm@osdl.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: modules in 2.6 kernel - question for FAQ?
Date: Thu, 15 Apr 2004 09:41:59 -0400 [thread overview]
Message-ID: <407E9127.8070303@nortelnetworks.com> (raw)
In-Reply-To: <1082004860.17780.143.camel@bach>
Rusty Russell wrote:
> They can only do this if they're not using the kernel makefiles. So I
> don't really think it's a priority...
Unfortunately some of us have no choice but to use binary-only drivers.
This is starting to change, but they are currently still needed for some
hardware.
Chris
next prev parent reply other threads:[~2004-04-15 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200404142142.41137.arekm@pld-linux.org>
2004-04-15 1:52 ` modules in 2.6 kernel - question for FAQ? Rusty Russell
2004-04-15 4:44 ` Sam Ravnborg
2004-04-15 4:54 ` Rusty Russell
2004-04-15 13:41 ` Chris Friesen [this message]
2004-04-15 13:56 ` Arjan van de Ven
2004-04-15 14:57 ` Chris Friesen
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=407E9127.8070303@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=akpm@osdl.org \
--cc=arekm@pld-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.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