All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luciano Coelho <coelho@ti.com>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
	linville@tuxdriver.com
Subject: Re: [PATCH 1/3] cfg80211/nl80211: add support for scheduled scans
Date: Mon, 09 May 2011 16:59:53 +0300	[thread overview]
Message-ID: <1304949593.12586.547.camel@cumari> (raw)
In-Reply-To: <BANLkTinfovOLWL1b57kpV5S_LeUMbCatHQ@mail.gmail.com>

On Mon, 2011-05-09 at 12:50 +0300, Eliad Peller wrote:
> On Thu, May 5, 2011 at 4:00 PM, Luciano Coelho <coelho@ti.com> wrote:
> > Implement new functionality for scheduled scan offload.  With this feature we
> > can scan automatically at certain intervals.
> >
> > The idea is that the hardware can perform scan automatically and filter on
> > desired results without waking up the host unnecessarily.
> >
> > Add NL80211_CMD_START_SCHED_SCAN and NL80211_CMD_STOP_SCHED_SCAN
> > commands to the nl80211 interface.  When results are available they are
> > reported by NL80211_CMD_SCHED_SCAN_RESULTS events.  The userspace is
> > informed when the scheduled scan has stopped with a
> > NL80211_CMD_SCHED_SCAN_STOPPED event, which can be triggered either by
> > the driver or by a call to NL80211_CMD_STOP_SCHED_SCAN.
> >
> > Signed-off-by: Luciano Coelho <coelho@ti.com>
> > ---
> [...]
> 
> > +
> > +       err = rdev->ops->sched_scan_start(&rdev->wiphy, dev, request);
> > +       if (!err)
> > +               nl80211_send_sched_scan(rdev, dev,
> > +                                       NL80211_CMD_START_SCHED_SCAN);
> > +       else {
> > +out_free:
> > +               kfree(request);
> > +               rdev->sched_scan_req = NULL;
> > +       }
> > +
> > +       return err;
> > +}
> 
> i know it's the same in nl80211_trigger_scan(), but it still looks
> very odd - goto into else block?!

Good point, looks a bit ugly and it was indeed copied.  I'll clean it up
a bit.

-- 
Cheers,
Luca.


  reply	other threads:[~2011-05-09 13:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 13:00 [PATCH 0/3] cfg80211/mac80211: implementation of scheduled scan Luciano Coelho
2011-05-05 13:00 ` [PATCH 1/3] cfg80211/nl80211: add support for scheduled scans Luciano Coelho
2011-05-09  8:12   ` Johannes Berg
2011-05-09  8:17     ` Luciano Coelho
2011-05-09  8:23       ` Johannes Berg
2011-05-09  8:25         ` Luciano Coelho
2011-05-09  9:50   ` Eliad Peller
2011-05-09 13:59     ` Luciano Coelho [this message]
2011-05-05 13:00 ` [PATCH 2/3] mac80211: add support for HW scheduled scan Luciano Coelho
2011-05-09  8:22   ` Johannes Berg
2011-05-09  8:22     ` Johannes Berg
2011-05-09 13:38     ` Luciano Coelho
2011-05-05 13:00 ` [PATCH 3/3] cfg80211/nl80211: add interval attribute for scheduled scans Luciano Coelho
2011-05-05 14:43   ` Ben Greear
2011-05-05 14:51     ` Johannes Berg
2011-05-05 14:50       ` Ben Greear
2011-05-05 14:58         ` Johannes Berg
2011-05-05 14:59           ` Johannes Berg
2011-05-05 15:48             ` Luciano Coelho
2011-05-05 15:51               ` Luciano Coelho
2011-05-05 16:13                 ` Johannes Berg
2011-05-05 16:22                   ` Ben Greear
2011-05-05 16:29                     ` Luciano Coelho

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=1304949593.12586.547.camel@cumari \
    --to=coelho@ti.com \
    --cc=eliad@wizery.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.