From: Bob Copeland <me@bobcopeland.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Xu, Martin" <martin.xu@intel.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"yang.y.yi@gmail.com" <yang.y.yi@gmail.com>,
Vikram Kandukuri <Vikram.Kandukuri@atheros.com>,
Jothikumar Mothilal <Jothikumar.Mothilal@atheros.com>,
"ath5k-devel@lists.ath5k.org" <ath5k-devel@lists.ath5k.org>,
"Liu, Bing Wei" <bing.wei.liu@intel.com>,
"Selbak, Rolla N" <rolla.n.selbak@intel.com>,
"Wang, Yong Y" <yong.y.wang@intel.com>
Subject: Re: [ath5k-devel] [Bug 11749] Ath5k driver has too many interrupts per second at idle
Date: Sun, 23 Nov 2008 17:27:36 -0500 [thread overview]
Message-ID: <20081123222735.GB30249@hash.localnet> (raw)
In-Reply-To: <20081121202734.GC3540@tuxdriver.com>
On Fri, Nov 21, 2008 at 03:27:34PM -0500, John W. Linville wrote:
> > +static void ath5k_bss_info_changed(struct ieee80211_hw *hw,
> > + struct ieee80211_vif *vif,
> > + struct ieee80211_bss_conf *bss_conf,
> > + u32 changes);
>
> This patch defines ath5k_bss_info_changed, but doesn't use it.
> Is that really what you meant to do?
The first version of this patch set .bss_info_changed but it looks
like it got lost along the way. Martin?
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2008-11-23 22:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11749-13098@http.bugzilla.kernel.org/>
[not found] ` <20081013150525.884BC108058@picon.linux-foundation.org>
2008-10-13 19:06 ` [Bug 11749] Ath5k driver has too many interrupts per second at idle Luis R. Rodriguez
2008-10-13 19:14 ` [ath5k-devel] " Nick Kossifidis
2008-11-13 6:12 ` Xu, Martin
2008-11-13 16:26 ` Bob Copeland
2008-11-17 7:35 ` Xu, Martin
2008-11-17 13:37 ` Bob Copeland
2008-11-20 3:13 ` Xu, Martin
2008-11-20 22:01 ` Bob Copeland
2008-11-20 22:41 ` Luis R. Rodriguez
2008-11-21 20:27 ` John W. Linville
2008-11-23 22:27 ` Bob Copeland [this message]
2008-11-24 2:49 ` Xu, Martin
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=20081123222735.GB30249@hash.localnet \
--to=me@bobcopeland.com \
--cc=Jothikumar.Mothilal@atheros.com \
--cc=Vikram.Kandukuri@atheros.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=bing.wei.liu@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=martin.xu@intel.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
--cc=rolla.n.selbak@intel.com \
--cc=yang.y.yi@gmail.com \
--cc=yong.y.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.