From: Grazvydas Ignotas <notasas@gmail.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Cc: "Pavel Machek" <pavel@ucw.cz>,
"Pali Rohár" <pali.rohar@gmail.com>,
"David Gnedt" <david.gnedt@davizone.at>,
"Grazvydas Ignotas" <notasas@gmail.com>
Subject: Re: [PATCH 0/4] wl1251 IBSS fixes
Date: Fri, 9 May 2014 03:21:21 +0300 [thread overview]
Message-ID: <CANOLnOO0xPH9kfZuqdbpYkdQrOFAOvL-4H0QmfAUVKCwg0ot2Q@mail.gmail.com> (raw)
In-Reply-To: <1398125395-5579-1-git-send-email-notasas@gmail.com>
On Tue, Apr 22, 2014 at 3:09 AM, Grazvydas Ignotas <notasas@gmail.com> wrote:
> IBSS mode is currently advertised by wl1251 driver but is totally broken.
> First there is a disconnect hack for monitor mode that was recently merged,
> it abuses mac80211 and causes corruption in IBSS mode, so I think should be
> reverted. Then there are several cases of station-only mac80211 functions
> called carelessly, what is also fixed.
Ping.
This driver is orphan and hardware carrying it is outdated, so acks /
tested-bys are unlikely..
--
Gražvydas
next prev parent reply other threads:[~2014-05-09 0:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 0:09 [PATCH 0/4] wl1251 IBSS fixes Grazvydas Ignotas
2014-04-22 0:09 ` [PATCH 1/4] Revert "wl1251: enforce changed hw encryption support on monitor state change" Grazvydas Ignotas
2014-04-22 0:09 ` [PATCH 2/4] wl1251: fix null data for IBSS Grazvydas Ignotas
2014-04-22 0:09 ` [PATCH 3/4] wl1251: fix mixed up args for join Grazvydas Ignotas
2014-04-22 0:09 ` [PATCH 4/4] wl1251: only call ieee80211_beacon_loss in managed mode Grazvydas Ignotas
2014-05-09 0:21 ` Grazvydas Ignotas [this message]
2014-05-09 20:03 ` [PATCH 0/4] wl1251 IBSS fixes Pali Rohár
2014-05-10 12:28 ` Pali Rohár
2014-05-30 16:18 ` Pali Rohár
2014-05-31 13:15 ` Grazvydas Ignotas
2014-05-31 13:20 ` Pali Rohár
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=CANOLnOO0xPH9kfZuqdbpYkdQrOFAOvL-4H0QmfAUVKCwg0ot2Q@mail.gmail.com \
--to=notasas@gmail.com \
--cc=david.gnedt@davizone.at \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
/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).