linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Thirumalai <tpachamu@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>,
	ath6kl-devel <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH 0/4] Enable uAPSD support in AP mode
Date: Mon, 9 Jan 2012 13:37:15 +0200	[thread overview]
Message-ID: <4F0AD16B.6010709@qca.qualcomm.com> (raw)
In-Reply-To: <1326095083-1538-1-git-send-email-tpachamu@qca.qualcomm.com>

On 01/09/2012 09:44 AM, Thirumalai wrote:
> In addition to legacy power save, this series of patch adds
> support for uAPSD in AP mode.
> 
> When connected station goes into suspend state, the driver will
> start queuing pkts in the separate queue (called uapsd queue)
> until the station ask for it. 
> 
> The moment driver starting queuing, it will enable traffic indication
> bit for the client connected to indicate data availability. 
> Once station ask for the data (via Trigger frame), the driver will 
> dequeue and send pkt one by one to the station.

I didn't do very thorough review but here are my first comments:

I see that you enable uapsd in patch 2 but add more functionality in
patches 3 and 4. That will break bisect as uapsd will be broken between
patches 2 and 4, no?

It's nice to have small patches, but it's more important to make sure
that bisect works. So you could just fold patches 2-4 into one. You
could even fold patch 1, as it doesn't give any benefit, and just have
one big patch adding the support. Or alternatively you need to enable
uapsd in the last patch so that it won't be used until all the code is
in place.

There are also some sparse warnings:

drivers/net/wireless/ath/ath6kl/wmi.h:232:21: warning: invalid
assignment: |=
drivers/net/wireless/ath/ath6kl/wmi.h:232:21:    left side has type
restricted __le16
drivers/net/wireless/ath/ath6kl/wmi.h:232:21:    right side has type int
drivers/net/wireless/ath/ath6kl/txrx.c:109:36: warning: incorrect type
in assignment (different base types)
drivers/net/wireless/ath/ath6kl/txrx.c:109:36:    expected unsigned
short [unsigned] [usertype] ether_type
drivers/net/wireless/ath/ath6kl/txrx.c:109:36:    got restricted __be16
[usertype] h_proto
drivers/net/wireless/ath/ath6kl/txrx.c:110:29: warning: cast to
restricted __be16
drivers/net/wireless/ath/ath6kl/txrx.c:110:29: warning: cast to
restricted __be16
drivers/net/wireless/ath/ath6kl/txrx.c:110:29: warning: cast to
restricted __be16
drivers/net/wireless/ath/ath6kl/txrx.c:110:29: warning: cast to
restricted __be16
drivers/net/wireless/ath/ath6kl/txrx.c:117:44: warning: incorrect type
in assignment (different base types)
drivers/net/wireless/ath/ath6kl/txrx.c:117:44:    expected unsigned
short [unsigned] [usertype] ether_type
drivers/net/wireless/ath/ath6kl/txrx.c:117:44:    got restricted __be16
[usertype] eth_type
drivers/net/wireless/ath/ath6kl/txrx.c:121:43: warning: restricted
__be16 degrades to integer
drivers/net/wireless/ath/ath6kl/txrx.c:1360:41: warning: restricted
__le16 degrades to integer

And please use your full name in the signed off by line.

Kalle

      parent reply	other threads:[~2012-01-09 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  7:44 [PATCH 0/4] Enable uAPSD support in AP mode Thirumalai
2012-01-09  8:54 ` Johannes Berg
2012-01-09 11:46   ` Kalle Valo
2012-01-10 17:38     ` Pachamuthu, Thirumalai
2012-01-09 11:37 ` 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=4F0AD16B.6010709@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tpachamu@qca.qualcomm.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).