From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Lurkos <lurkos.usenet@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Merge compat-wireless-old into 2.6.26
Date: Tue, 10 Feb 2009 10:19:15 -0800 [thread overview]
Message-ID: <20090210181915.GA4248@tesla> (raw)
In-Reply-To: <20090210172817.9004.60065.XPN@L622132.user.x-privat.org>
On Tue, Feb 10, 2009 at 09:28:16AM -0800, Lurkos wrote:
> Is it possibile to patch linux 2.6.26 source (e.g. Debian Lenny sources)
> to have the new compat-wireless-old?
> If yes, what could be the correct procedure?
It is possible, you would just have to replace the directories
that compat-wireless-old has in the kernel sources.
> I would prefer to compile only my wireless network card driver
> statically into the kernel.
What exactly will that buy you though? Is it worth the effort?
Luis
next prev parent reply other threads:[~2009-02-10 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 17:28 Merge compat-wireless-old into 2.6.26 Lurkos
2009-02-10 18:19 ` Luis R. Rodriguez [this message]
2009-02-11 18:17 ` Lurkos
2009-02-12 0:59 ` Hin-Tak Leung
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=20090210181915.GA4248@tesla \
--to=lrodriguez@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lurkos.usenet@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 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).