All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: Stop scheduled scan if netlink client disappears
Date: Tue, 11 Nov 2014 15:54:55 +0100	[thread overview]
Message-ID: <1415717695.2163.6.camel@sipsolutions.net> (raw)
In-Reply-To: <1415716059-608-1-git-send-email-jukka.rissanen@linux.intel.com> (sfid-20141111_152746_888050_18874AA2)

On Tue, 2014-11-11 at 16:27 +0200, Jukka Rissanen wrote:
> A new attribute NL80211_ATTR_SCAN_SOCKET_OWNER can be set by the
> scan initiator. If present, the attribute will cause the scan to
> be stopped if the client dies.

We already have NL80211_ATTR_IFACE_SOCKET_OWNER, maybe we can repurpose
this flag to a more general "owner" flag?

Of course we need to keep ABI (same attribute number) and API (a
#define) but that's not an issue.

johannes


  reply	other threads:[~2014-11-11 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 14:27 [PATCH] nl80211: Stop scheduled scan if netlink client disappears Jukka Rissanen
2014-11-11 14:54 ` Johannes Berg [this message]
2014-11-11 14:56 ` Johannes Berg

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=1415717695.2163.6.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jukka.rissanen@linux.intel.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 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.