linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vivek Natarajan <vivek.natraj@gmail.com>,
	linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	IvDoorn@gmail.com, gwingerde@gmail.com
Subject: Re: [PATCH v3] mac80211: Retry null data frame for power save.
Date: Mon, 8 Feb 2010 21:30:09 +0100	[thread overview]
Message-ID: <201002082130.10238.chunkeey@googlemail.com> (raw)
In-Reply-To: <1265646279.3783.8.camel@johannes.berg>

On Monday 08 February 2010 17:24:39 Johannes Berg wrote:
> On Mon, 2010-02-08 at 18:43 +0530, Vivek Natarajan wrote:
> 
> > > On a related issue: What about _inverting_ the flag, so it will
> > > be set for devices which can't give any accurate tx_status
> > > information. This has the advantage that we don't have to touch
> > > other drivers?
> > 
> > Shall I rename it as HW_NO_TX_ACK_REPORT?
> > Looking at the other flags, they show some positively present
> > feature in the hw. In those lines, HW_REPORTS_TX_ACK_STATUS
> > might be better.
> 
> The positive feature flag has the advantage that we don't have to touch
> any of the essentially unmaintained drivers, so I much prefer having it
> that way so maintainers can enable the flag after testing etc.

Alright. I count 2:1 votes. So "positive feature flag" it is.

BTW: I added rt2x00 project maintainers to the CC, because
If I'm not totally wrong, this patch _reduces_ some PS
features of rt2x00. This is because not all of rt2x00
supported & PS-capable/enabled devices return a proper tx_status
and therefore these devices will be the most affected AFAICT.

Any word from you guys? Or have you scrubbed the PS features already?

Regards,
	Chr

  reply	other threads:[~2010-02-08 20:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 12:17 [PATCH v3] mac80211: Retry null data frame for power save Vivek Natarajan
2010-02-08 12:17 ` [PATCH] mac80211: Reset dynamic ps timer in Rx path Vivek Natarajan
2010-02-08 12:42 ` [PATCH v3] mac80211: Retry null data frame for power save Christian Lamparter
2010-02-08 13:13   ` Vivek Natarajan
2010-02-08 16:24     ` Johannes Berg
2010-02-08 20:30       ` Christian Lamparter [this message]
2010-02-08 21:02         ` Christian Lamparter
2010-02-09  7:57 ` Johannes Berg
2010-02-09  8:36   ` Vivek Natarajan
2010-02-09  8:57     ` 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=201002082130.10238.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=IvDoorn@gmail.com \
    --cc=gwingerde@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=vivek.natraj@gmail.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).