From: Dan Williams <dcbw@redhat.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: linux-wireless@vger.kernel.org, ipw2100-devel@lists.sourceforge.net
Subject: Re: [PATCH] ipw2100: send WEXT scan events
Date: Mon, 22 Oct 2007 11:46:27 -0400 [thread overview]
Message-ID: <1193067987.30205.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1193041255.3069.164.camel@debian.sh.intel.com>
On Mon, 2007-10-22 at 16:20 +0800, Zhu Yi wrote:
> On Wed, 2007-10-10 at 12:28 -0400, Dan Williams wrote:
> > ipw2100 wasn't sending WEXT scan events at all on scan completion.
> > And
> > like ipw2200, the driver aggressively auto-scans, requiring
> > non-user-requested scan events to be batched together and sent at
> > specific intervals instead of many times per seconds.
> >
> > Signed-off-by: Dan Williams <dcbw@redhat.com>
>
> Sorry for the late response. Please see my comments below.
>
> > + queue_delayed_work(priv->workqueue,
> > + &priv->scan_event_later,
> > + round_jiffies(msecs_to_jiffies(4000)));
>
> round_jiffies_relative instead?
Yeah, that patch hit after I posted mine. Can fix up.
> > @@ -6118,6 +6153,8 @@ static struct net_device
> > *ipw2100_alloc_device(struct pci_dev *pci_dev,
> > INIT_DELAYED_WORK(&priv->wx_event_work,
> > ipw2100_wx_event_work);
> > INIT_DELAYED_WORK(&priv->hang_check, ipw2100_hang_check);
> > INIT_DELAYED_WORK(&priv->rf_kill, ipw2100_rf_kill);
> > + INIT_WORK(&priv->scan_event_now, ipw2100_scan_event_now);
> > + INIT_DELAYED_WORK(&priv->scan_event_later,
> > ipw2100_scan_event_later);
>
> Except the work vs. delayed_work, they are doing the same thing. So you
> can replace scan_event_now by scan_event_later with delay = 0.
Good catch, will post update.
Thanks!
Dan
next prev parent reply other threads:[~2007-10-22 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 16:28 [PATCH] ipw2100: send WEXT scan events Dan Williams
2007-10-22 8:20 ` Zhu Yi
2007-10-22 15:46 ` Dan Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-26 21:04 [PATCH] Add get_unaligned to ieee80211_get_radiotap_len John W. Linville
2007-10-26 21:04 ` [PATCH] Improve sanity checks on injected packets John W. Linville
2007-10-26 21:04 ` [PATCH] mac80211: filter locally-originated multicast frames John W. Linville
2007-10-26 21:04 ` [PATCH] libertas: fix endianness breakage John W. Linville
2007-10-26 21:04 ` [PATCH] libertas: more " John W. Linville
2007-10-26 21:04 ` [PATCH] ieee80211: fix TKIP QoS bug John W. Linville
2007-10-26 21:04 ` [PATCH] mac80211: reorder association debug output John W. Linville
2007-10-26 21:04 ` [PATCH] mac80211: store channel info in sta_bss_list John W. Linville
2007-10-26 21:04 ` [PATCH] mac80211: store SSID " John W. Linville
2007-10-26 21:04 ` [PATCH] mac80211: honor IW_SCAN_THIS_ESSID in siwscan ioctl John W. Linville
2007-10-26 21:04 ` [PATCH] mac80211: only honor IW_SCAN_THIS_ESSID in STA, IBSS, and AP modes John W. Linville
2007-10-26 21:04 ` [PATCH] mac80211: make ieee802_11_parse_elems return void John W. Linville
2007-10-26 21:04 ` [PATCH] zd1201: avoid null ptr access of skb->dev John W. Linville
2007-10-26 21:04 ` [PATCH] ipw2100: send WEXT scan events John W. Linville
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=1193067987.30205.11.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=yi.zhu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox