linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Dan Williams <dcbw@redhat.com>, Thomas Pedersen <thomas@cozybit.com>
Subject: [RFC 0/3] mesh/wds channel changes & clarifications
Date: Fri, 11 May 2012 20:08:17 +0200	[thread overview]
Message-ID: <20120511180817.974687689@sipsolutions.net> (raw)

This shows the direction I want to take the cfg80211
APIs in wrt. channel settings.

After these patches, there is no more set_channel(),
and set_monitor_channel() is only available when you
 * set the channel on a wiphy
 * set the channel on a monitor netdev
 * set the channel using wext on an unassociated
   managed interface

All these translate into setting the monitor channel
though.

The sole exception is for libertas, so I split that
out into a new function that only it will ever have.
Not the best thing to do, but I don't really see any
good choice that doesn't break libertas.

Note that this requires a lot of patches I've sent
over the last two days, or you can find all of them
on http://j.sipsolutions.net/patches/kernel/all/LATEST/

johannes

             reply	other threads:[~2012-05-11 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 18:08 Johannes Berg [this message]
2012-05-11 18:08 ` [RFC 1/3] cfg80211: provide channel to join_mesh function Johannes Berg
2012-05-11 19:10   ` Thomas Pedersen
2012-05-11 19:15     ` Johannes Berg
2012-05-11 18:08 ` [RFC 2/3] cfg80211: disallow setting channel on WDS interfaces Johannes Berg
2012-05-11 18:08 ` [RFC 3/3] cfg80211: clarify set_channel APIs 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=20120511180817.974687689@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=thomas@cozybit.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;
as well as URLs for NNTP newsgroup(s).