From: Johannes Berg <johannes@sipsolutions.net>
To: Hong Liu <hong.liu@intel.com>
Cc: Jiri Benc <jbenc@suse.cz>,
netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 2/2]d80211: add hardware scan callback
Date: Fri, 01 Sep 2006 08:41:03 +0200 [thread overview]
Message-ID: <1157092863.2878.13.camel@ux156> (raw)
In-Reply-To: <1157081867.11040.41.camel@devlinux-hong>
On Fri, 2006-09-01 at 11:37 +0800, Hong Liu wrote:
>
> + local->sta_scanning = 1;
> + if (local->hw->hw_scan)
> + return local->hw->hw_scan(dev, ssid, ssid_len);
> +
My question still stands, is it proper to assign sta_scanning to 1 even
if the function returns an error?
johannes
next prev parent reply other threads:[~2006-09-01 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 8:32 [PATCH 2/2]d80211: add hardware scan callback Hong Liu
2006-08-29 12:08 ` Johannes Berg
2006-08-30 17:10 ` Jiri Benc
2006-08-30 18:36 ` Mohamed Abbas
2006-09-01 3:37 ` Hong Liu
2006-09-01 6:41 ` Johannes Berg [this message]
2006-09-01 7:34 ` Hong Liu
2006-09-21 19:22 ` Jiri Benc
2009-04-06 15:12 ` oterito
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=1157092863.2878.13.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=hong.liu@intel.com \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).