From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull-request: mac80211 2015-11-26
Date: Wed, 02 Dec 2015 10:46:50 +0100 [thread overview]
Message-ID: <1449049610.2449.3.camel@sipsolutions.net> (raw)
In-Reply-To: <1448552352.2167.14.camel@sipsolutions.net> (sfid-20151126_163919_664516_CC0F7608)
Hi,
> ----------------------------------------------------------------
> A small set of fixes for 4.4:
> * remove NL80211_FEATURE_FULL_AP_CLIENT_STATE again, it
> was broken and needs more work, we'll enable it for 4.5
> * fix call_rcu() induced use-after-reset/free in mesh
> (that was suddenly causing issues in certain tests)
> * always request block-ack window size 64 as we found
> some APs will otherwise crash (really ...)
> * fix P2P-Device teardown sequence to avoid restarting
> with uninitialized data
I've got two more fairly important changes - one for regulatory issues
and one for an uninitialized variable that was leading to fairly
obscure bugs - do you prefer I wait, or send a new pull request
covering this one plus the two new fixes?
Thanks,
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: pull-request: mac80211 2015-11-26
Date: Wed, 02 Dec 2015 10:46:50 +0100 [thread overview]
Message-ID: <1449049610.2449.3.camel@sipsolutions.net> (raw)
In-Reply-To: <1448552352.2167.14.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> (sfid-20151126_163919_664516_CC0F7608)
Hi,
> ----------------------------------------------------------------
> A small set of fixes for 4.4:
> * remove NL80211_FEATURE_FULL_AP_CLIENT_STATE again, it
> was broken and needs more work, we'll enable it for 4.5
> * fix call_rcu() induced use-after-reset/free in mesh
> (that was suddenly causing issues in certain tests)
> * always request block-ack window size 64 as we found
> some APs will otherwise crash (really ...)
> * fix P2P-Device teardown sequence to avoid restarting
> with uninitialized data
I've got two more fairly important changes - one for regulatory issues
and one for an uninitialized variable that was leading to fairly
obscure bugs - do you prefer I wait, or send a new pull request
covering this one plus the two new fixes?
Thanks,
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-02 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 15:39 pull-request: mac80211 2015-11-26 Johannes Berg
2015-11-26 15:39 ` Johannes Berg
2015-12-02 9:46 ` Johannes Berg [this message]
2015-12-02 9:46 ` Johannes Berg
2015-12-02 20:43 ` David Miller
2015-12-02 21:42 ` pull-request: mac80211 2015-12-02 Johannes Berg
2015-12-03 20:58 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-11-26 15:37 pull-request: mac80211 2015-11-26 Johannes Berg
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=1449049610.2449.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.