From: Kalle Valo <kvalo@codeaurora.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: fix moredata flag endianness in cabq tx
Date: Tue, 21 Jul 2015 15:01:56 +0000 (UTC) [thread overview]
Message-ID: <20150721150156.DCA2D141ACC@smtp.codeaurora.org> (raw)
In-Reply-To: <1436437642-18781-1-git-send-email-michal.kazior@tieto.com>
> While compiling ath9k with some extra flags I've
> found that:
>
> ath9k/xmit.c +2473 ## 16: warning: restricted __le16 degrades to integer
> ath9k/xmit.c +2474 ## 36: warning: invalid assignment: &=
> ath9k/xmit.c +2474 ## 36: left side has type restricted __le16
> ath9k/xmit.c +2474 ## 36: right side has type int
>
> There's no way for frame ftype/stype to be
> mistreated as the offending 'moredata' flag when
> considering cab queue.
>
> This could've however theoretically led sometimes
> to increased power consumption on connected
> stations as they would keep their Rx active
> waiting for frames that would never come.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
prev parent reply other threads:[~2015-07-21 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 10:27 [ath9k-devel] [PATCH] ath9k: fix moredata flag endianness in cabq tx Michal Kazior
2015-07-21 15:01 ` Kalle Valo [this message]
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=20150721150156.DCA2D141ACC@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath9k-devel@lists.ath9k.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