linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Given an interface, how to tell if it's associated?
Date: Tue, 28 Sep 2010 09:23:33 +0200	[thread overview]
Message-ID: <1285658613.3885.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4CA12600.5070304@candelatech.com>

On Mon, 2010-09-27 at 16:17 -0700, Ben Greear wrote:
> I need to iterate through all local->interfaces and
> if they are stations, figure out if they are associated
> or not.
> 
> I tried checking for existence of sdata->u.mgd.associated,
> but it is always null (I'm using non-encrypted links
> currently, in case that matters.)

That's correct, if it's always NULL then you're not associated properly
I guess?

johannes


  reply	other threads:[~2010-09-28  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 23:17 Given an interface, how to tell if it's associated? Ben Greear
2010-09-28  7:23 ` Johannes Berg [this message]
2010-09-28 13:40   ` Ben Greear

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=1285658613.3885.2.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@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).