From: Johannes Berg <johannes@sipsolutions.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Ben Greear <greearb@candelatech.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT/FYI] mac80211: revert on-channel work optimisations
Date: Fri, 25 Nov 2011 12:29:09 +0100 [thread overview]
Message-ID: <1322220549.4123.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20111125112732.GA19885@redhat.com> (sfid-20111125_122507_960511_AA3BCEDE)
On Fri, 2011-11-25 at 12:27 +0100, Stanislaw Gruszka wrote:
> On Tue, Nov 08, 2011 at 07:38:51PM +0100, Johannes Berg wrote:
> > I was looking at RH bug 731365 but I think Eliad's patches should have
> > fixed that. But generally, that code just makes me nervous, in
> > particular ieee80211_cfg_on_oper_channel(). I think all of this should
> > be a lot simpler, and if it isn't that's probably due to *other* bugs
> > this is working around.
>
> So, can proceed with that revert? We just get confirmation in
> RH bug 731365, that it fix reproducible rate_control_send_low
> WARNING issue (also is probable that it fix some rtlwifi problems,
> but I do not have clear confirmation about that yet).
Ok let's do it -- I have this patch for upstream, can you later provide
the one for stable?
johannes
next prev parent reply other threads:[~2011-11-25 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 17:10 [RFT/FYI] mac80211: revert on-channel work optimisations Johannes Berg
2011-11-08 17:17 ` Ben Greear
2011-11-08 17:18 ` Johannes Berg
2011-11-08 17:25 ` Ben Greear
2011-11-08 17:56 ` Johannes Berg
2011-11-08 18:08 ` Ben Greear
2011-11-08 18:38 ` Johannes Berg
2011-11-25 11:27 ` Stanislaw Gruszka
2011-11-25 11:29 ` Johannes Berg [this message]
2012-02-17 15:44 ` Johannes Berg
2012-02-17 16:13 ` Ben Greear
2012-02-17 18:19 ` Johannes Berg
2012-02-17 18:38 ` Ben Greear
2012-02-18 17:39 ` Stanislaw Gruszka
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=1322220549.4123.7.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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).