From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
alexandre.f.demers@gmail.com, linville@tuxdriver.com
Subject: Re: r92su: status and will it be merged anytime soon?
Date: Mon, 04 Nov 2013 19:32:45 +0100 [thread overview]
Message-ID: <1383589965.14295.18.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <8287832.vyseD3v7Cm@blech> (sfid-20131104_171958_354595_246E4CB6)
On Mon, 2013-11-04 at 17:19 +0100, Christian Lamparter wrote:
> Yes, there is even more duplicated code if you factor in the (de-)fragmentation
> and deaggregation code from mac80211. Furthermore r92su could be sharing a bit
> of infrastructure with rtlwifi.
Yeah, that some of that seems to be duplicated in mwifiex too. I think
there'd be some benefit in trying to share more. Maybe moving some to
cfg80211? Or some new module?
> I didn't include lib80211 since it reports mic failures via WEXT:
> wireless_send_event(dev, IWEVMICHAELMICFAILURE, &wrqu, (char *)&ev);
> (And I don't think this can be changed easily without touching ipw2200
> and hostap-driver).
Yeah that'd be tricky, though I guess you could pass a wdev pointer and
allow it to be NULL or so.
johannes
next prev parent reply other threads:[~2013-11-04 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 14:17 r92su: status and will it be merged anytime soon? Xose Vazquez Perez
2013-11-04 14:21 ` Johannes Berg
2013-11-04 15:34 ` Larry Finger
2013-11-04 15:47 ` Christian Lamparter
2013-11-04 16:04 ` Johannes Berg
2013-11-04 16:15 ` Joshua Roys
2013-11-04 16:19 ` Christian Lamparter
2013-11-04 18:32 ` Johannes Berg [this message]
2013-11-04 19:10 ` Alexandre Demers
2013-11-04 16:06 ` Xose Vazquez Perez
2013-11-04 16:22 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2013-11-02 20:19 Alexandre Demers
2013-11-02 21:50 ` Christian Lamparter
2013-11-02 21:53 ` Larry Finger
2013-11-02 22:36 ` Alexandre Demers
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=1383589965.14295.18.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=alexandre.f.demers@gmail.com \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=xose.vazquez@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