From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless in linux
Date: Tue, 30 Nov 2010 17:07:07 -0600 [thread overview]
Message-ID: <4CF5839B.6060700@lwfinger.net> (raw)
In-Reply-To: <AANLkTimXDZLm7CAn7VyRPxQscTfHwTNALbDOh3LpjSQc@mail.gmail.com>
On 11/30/2010 04:16 PM, Luis R. Rodriguez wrote:
> http://lmgtfy.com/?q=Linux+wireless
Good one.
I have a separate question about compat-wireless. I need to backport to kernel
2.6.21. I have fixed most of the problems, but I'm stuck on the case where
something has been added to a struct since that kernel. I looked at all the
compat-XXX patches, but I don't see what has been done previously. Is that
written up somewhere, or is there a prescription?
Thanks,
Larry
next prev parent reply other threads:[~2010-11-30 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 22:05 wireless in linux Heyendal, Carl
2010-11-30 22:16 ` Luis R. Rodriguez
2010-11-30 23:07 ` Larry Finger [this message]
2010-12-01 13:57 ` Heyendal, Carl
2010-12-01 16:55 ` Heyendal, Carl
2010-12-01 21:20 ` Holger Schurig
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=4CF5839B.6060700@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).