From: Krzysztof Halasa <khc@pm.waw.pl>
To: Giridhar Pemmasani <giri@lmc.cs.sunysb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: About 4k kernel stack size....
Date: Wed, 21 Dec 2005 21:14:20 +0100 [thread overview]
Message-ID: <m3d5jq2oo3.fsf@defiant.localdomain> (raw)
In-Reply-To: <dobr1u$19t$1@sea.gmane.org> (Giridhar Pemmasani's message of "Wed, 21 Dec 2005 10:07:01 -0500")
Giridhar Pemmasani <giri@lmc.cs.sunysb.edu> writes:
> As I see, although people that rely on
> ndiswrapper (since there is no other way they could use the hardware that
> they have) will not be able to use their wireless cards when this patch
> gets merged without having to patch the kernel
Huh? -mm is already a patch so I'm not sure what users are you talking
about. End-users (non-developers) using -mm kernel (binary?) provided
by their distribution? Why would they want to use ndiswrapper (= binary
drivers, which make all bug reports and in fact all development
pointless) with devel kernel?
--
Krzysztof Halasa
next prev parent reply other threads:[~2005-12-21 20:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 22:14 J.A. Magallon
2005-12-20 2:52 ` Mark Lord
2005-12-20 13:37 ` Adrian Bunk
2005-12-20 14:37 ` Mike Snitzer
2005-12-20 15:00 ` Adrian Bunk
[not found] ` <46578.10.10.10.28.1135094132.squirrel@linux1>
2005-12-20 15:55 ` Sean
2005-12-21 15:07 ` Giridhar Pemmasani
2005-12-21 15:37 ` Kyle Moffett
2005-12-21 16:25 ` Giridhar Pemmasani
2005-12-21 16:46 ` Christoph Hellwig
2005-12-21 20:14 ` Krzysztof Halasa [this message]
2005-12-21 21:39 ` linux-os (Dick Johnson)
2005-12-22 9:14 ` Romano Giannetti
2005-12-20 17:02 ` linux-os (Dick Johnson)
2005-12-20 18:06 ` Chase Venters
2005-12-20 18:36 ` linux-os (Dick Johnson)
2005-12-20 18:43 ` Arjan van de Ven
2005-12-20 18:59 ` linux-os (Dick Johnson)
2005-12-20 22:33 ` Alan Cox
2005-12-20 22:54 ` Nikita Danilov
2005-12-21 14:02 ` linux-os (Dick Johnson)
2005-12-21 14:18 ` Nikita Danilov
2005-12-21 14:25 ` linux-os (Dick Johnson)
2005-12-21 15:19 ` Nikita Danilov
2005-12-21 22:50 ` Jan Engelhardt
2005-12-20 20:15 ` Alan Cox
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=m3d5jq2oo3.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=giri@lmc.cs.sunysb.edu \
--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
Powered by JetHome