From: Ali MJ Al-Nasrawy <alimjalnasrawy@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com
Subject: Re: [PATCH v3] brcmsmac: AP mode: update beacon when TIM changes
Date: Mon, 24 Sep 2018 13:24:54 +0300 [thread overview]
Message-ID: <20180924132454.1703045f@manjaro> (raw)
In-Reply-To: <1d03765b-2643-1c86-f0e7-b42664252f08@broadcom.com>
On Mon, 24 Sep 2018 10:15:49 +0200
Arend van Spriel <arend.vanspriel@broadcom.com> wrote:
> On 9/23/2018 11:54 AM, Ali MJ Al-Nasrawy wrote:
> > Beacons are not updated to reflect TIM changes. This is not
> > compliant with power-saving client stations as the beacons do not
> > have valid TIM and can cause the network to stall at random
> > occasions with highly variable latencies. Fix it by updating beacon
> > templates on mac80211 set_tim callback.
> >
> > Addresses an issue described in:
> > https://marc.info/?i=20180911163534.21312d08%20()%20manjaro
> >
> > Signed-off-by: Ali MJ Al-Nasrawy <alimjalnasrawy@gmail.com>
> > ---
>
> Missing 'v1 -> v2' in this changelog.
Sorry, missed that...
v1 -> v2:
-removed FIXME comment
-removed blank line before 'vif' member declaration
next prev parent reply other threads:[~2018-09-24 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 17:26 [PATCH] brcmsmac: ap mode: update beacon when TIM changes Ali MJ Al-Nasrawy
2018-09-20 12:04 ` Kalle Valo
2018-09-22 9:07 ` Arend van Spriel
2018-09-22 13:17 ` Ali MJ Al-Nasrawy
2018-09-22 13:41 ` [PATCH v2] brcmsmac: AP " Ali MJ Al-Nasrawy
2018-09-23 9:54 ` [PATCH v3] " Ali MJ Al-Nasrawy
2018-09-24 8:15 ` Arend van Spriel
2018-09-24 10:24 ` Ali MJ Al-Nasrawy [this message]
2018-09-26 9:04 ` Ali MJ Al-Nasrawy
2018-10-03 16:21 ` [PATCH v4] " Ali MJ Al-Nasrawy
2018-10-13 17:01 ` Kalle Valo
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=20180924132454.1703045f@manjaro \
--to=alimjalnasrawy@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=linux-wireless@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 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).