From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Kalle Valo <kalle.valo@nokia.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v3 4/4] mac80211: move dynamic_ps_timeout to hw.conf
Date: Mon, 1 Dec 2008 12:36:44 -0800 [thread overview]
Message-ID: <20081201203644.GN5992@tesla> (raw)
In-Reply-To: <1228160468.10627.42.camel@johannes.berg>
On Mon, Dec 01, 2008 at 11:41:07AM -0800, Johannes Berg wrote:
> On Mon, 2008-12-01 at 11:11 -0800, Luis R. Rodriguez wrote:
>
> > Would it be too much trouble to add this via cfg80211/nl80211 instead
> > or at least add both? The more we can push in that direction the
> > better.
>
> That would be good, but I don't think it's really a requirement right
> now since wext has the API we need already.
Sure, just wishful thinking.
Luis
next prev parent reply other threads:[~2008-12-01 20:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 19:49 [RFC v3] mac80211 dynamic power save Kalle Valo
2008-11-28 19:49 ` [RFC v3 1/4] mac80211: enable IEEE80211_CONF_PS only when associated Kalle Valo
2008-11-28 22:11 ` Johannes Berg
2008-11-29 6:50 ` Kalle Valo
2008-11-28 19:49 ` [RFC v3 2/4] mac80211: implement dynamic power save Kalle Valo
2008-11-28 22:14 ` Johannes Berg
2008-11-29 6:53 ` Kalle Valo
2008-12-01 19:10 ` Luis R. Rodriguez
2008-12-01 22:40 ` Johannes Berg
2008-12-01 23:49 ` Luis R. Rodriguez
2008-12-02 19:42 ` Kalle Valo
2008-11-28 19:49 ` [RFC v3 3/4] mac80211: add IEEE80211_HW_NO_DYNAMIC_PS flag Kalle Valo
2008-11-28 22:15 ` Johannes Berg
2008-11-29 6:55 ` Kalle Valo
2008-11-28 19:49 ` [RFC v3 4/4] mac80211: move dynamic_ps_timeout to hw.conf Kalle Valo
2008-11-28 22:18 ` Johannes Berg
2008-11-29 7:00 ` Kalle Valo
2008-12-01 19:11 ` Luis R. Rodriguez
2008-12-01 19:41 ` Johannes Berg
2008-12-01 20:36 ` Luis R. Rodriguez [this message]
2008-12-01 20:30 ` 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=20081201203644.GN5992@tesla \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).