From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [1/6] brcmfmac: fix skb priority handling
Date: Thu, 16 Jun 2016 15:21:02 +0000 (UTC) [thread overview]
Message-ID: <20160616152102.981CD6134F@smtp.codeaurora.org> (raw)
In-Reply-To: <1464989472-29684-2-git-send-email-arend.vanspriel@broadcom.com>
Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:
> From: Hante Meuleman <hante.meuleman@broadcom.com>
>
> SKBs can come with a prioriy. Currently a priority of 0..7 is
> assumed. But this assumption is incorrect. To fix this any
> priority of 0 or higher then 7 will be adjusted by calling
> cfg80211_classify8021d
>
> Reviewed-by: Arend Van Spriel <arend@broadcom.com>
> Reviewed-by: Franky Lin <franky.lin@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
> Signed-off-by: Hante Meuleman <hante.meuleman@broadcom.com>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Thanks, 6 patches applied to wireless-drivers-next.git:
10d096f708e8 brcmfmac: fix skb priority handling
d922dfa372ed brcmfmac: revise SDIO error message in brcmf_sdio_drivestrengthinit
cb39288fd6bb brcmfmac: use ndev->needed_headroom to reserve additional header space
43819926eda5 brcmfmac: add support for the PCIE devices 43525 and 43465
98aff6c005e3 brcmfmac: change rx_seq check log from error print to debug print
2a7344510286 brcm80211: update maintainers email addresses
--
Sent by pwcli
https://patchwork.kernel.org/patch/9154099/
next prev parent reply other threads:[~2016-06-16 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 21:31 [PATCH 0/6] brcm80211: contact info update and new devices Arend van Spriel
2016-06-03 21:31 ` [PATCH 1/6] brcmfmac: fix skb priority handling Arend van Spriel
2016-06-16 15:21 ` Kalle Valo [this message]
2016-06-03 21:31 ` [PATCH 2/6] brcmfmac: revise SDIO error message in brcmf_sdio_drivestrengthinit Arend van Spriel
2016-06-03 21:31 ` [PATCH 3/6] brcmfmac: use ndev->needed_headroom to reserve additional header space Arend van Spriel
2016-06-10 12:33 ` Kalle Valo
2016-06-03 21:31 ` [PATCH 4/6] brcmfmac: add support for the PCIE devices 43525 and 43465 Arend van Spriel
2016-06-03 21:31 ` [PATCH 5/6] brcmfmac: change rx_seq check log from error print to debug print Arend van Spriel
2016-06-10 12:36 ` Kalle Valo
2016-06-03 21:31 ` [PATCH 6/6] brcm80211: update maintainers email addresses Arend van Spriel
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=20160616152102.981CD6134F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=hante.meuleman@broadcom.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).