From: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>
To: "Yingying Zhao" <yingying.zhao@linux.intel.com>
Cc: "Tomas Winkler" <tomasw@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH]compat-2.6: fix compiling configurations for iwlwifi
Date: Thu, 17 Jul 2008 09:05:03 -0700 [thread overview]
Message-ID: <43e72e890807170905h5a261879u9d87963c621b57bf@mail.gmail.com> (raw)
In-Reply-To: <43e72e890807170621r25616966w1d542e4e235f9a3f@mail.gmail.com>
On Thu, Jul 17, 2008 at 6:21 AM, Luis R. Rodriguez
<mcgrof@winlab.rutgers.edu> wrote:
> On Thu, Jul 17, 2008 at 3:07 AM, Luis R. Rodriguez
> <mcgrof@winlab.rutgers.edu> wrote:
>> On Thu, Jul 17, 2008 at 3:04 AM, Yingying Zhao
>> <yingying.zhao@linux.intel.com> wrote:
>>
>>>> Also, was this tested with 2.6.22?
>>>>
>>>> Luis
>>> No. I just tested on 2.6.24.
>>> I'll wait for iwlwifi Kconfig is finalized by Tomas and retest this on
>>> 2.6.22.
>>
>> OK cool -- just a heads up then, I hadn't enabled LEDs or RFKILL
>> options for drivers as the framework needs backporting. Once
>> backported I expect it will compile well for older kernels.
>
> compat-wireless wasn't actually compiling for 2.6.22 anymore. I just
> fixed that. It loads mac80211. Either I did a mistake or we get an
> oops now when loading a driver on 2.6.22.
Yeah ok I can confirm there is a bug there on 2.6.22. We hit:
BUG_ON(!local || local->mdev == dev);
on ieee80211_i.h in IEEE80211_DEV_TO_SUB_IF()
Don't have time to debug this right now though.
Luis
next prev parent reply other threads:[~2008-07-17 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 8:15 [PATCH]compat-2.6: fix compiling configurations for iwlwifi Yingying Zhao
2008-07-17 8:29 ` Tomas Winkler
2008-07-17 9:48 ` Luis R. Rodriguez
2008-07-17 10:04 ` Yingying Zhao
2008-07-17 10:07 ` Luis R. Rodriguez
2008-07-17 13:21 ` Luis R. Rodriguez
2008-07-17 16:05 ` Luis R. Rodriguez [this message]
2008-07-17 16:12 ` Luis R. Rodriguez
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=43e72e890807170905h5a261879u9d87963c621b57bf@mail.gmail.com \
--to=mcgrof@winlab.rutgers.edu \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
--cc=yingying.zhao@linux.intel.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