All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 06/17] nl80211: prepare for non-netdev wireless devs
Date: Mon, 25 Jun 2012 16:12:14 +0200	[thread overview]
Message-ID: <1340633534.27437.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEeaG2i0LBOE6Jzsy6ghxpGRcDm3wUwi=+Vcmr9NcX96cw@mail.gmail.com> (sfid-20120625_154644_663761_77F9A61A)

On Mon, 2012-06-25 at 16:46 +0300, Eliad Peller wrote:

> > - * This structure must be allocated by the driver/stack
> > - * that uses the ieee80211_ptr field in struct net_device
> > - * (this is intentional so it can be allocated along with
> > - * the netdev.)
> > + * For netdevs, this structure must be allocated by the driver
> > + * that uses the ieee80211_ptr field in struct net_device (this
> > + * is intentional so it can be allocated along with the netdev.)
> > + * It need not be registered then as netdev registration will
> > + * be intercepted by cfg80211 to see the new wireless device.
> > + *
> it think you meant "it needs to be registered..." ?

Well, I should probably reword this, but I did actually mean that it
need not be registered (with cfg80211) if it has a netdev, because then
it must be registered as a netdev and "netdev registration will be
intercepted ..."

> > +       u32 identifier;

> > +       int devlist_generation, wdev_id;
> 
> it doesn't really matter, but why not define wdev_id with the same
> type as wdev->identifier?

I didn't even notice that, oops.

> > +       if (result)
> > +               return result;
> > +       return ERR_PTR(-ENODEV);
> 
> doesn't it remove the netns checks you've just added? :)

D'oh. Good point!

johannes


  reply	other threads:[~2012-06-25 14:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 14:50 [RFC 0/17] add P2P Device support Johannes Berg
2012-06-19 14:50 ` [RFC 01/17] cfg80211: make some functions static Johannes Berg
2012-06-19 14:50 ` [RFC 02/17] nl80211: refactor __cfg80211_rdev_from_info Johannes Berg
2012-06-19 14:50 ` [RFC 03/17] nl80211: fix netns separation Johannes Berg
2012-06-19 14:50 ` [RFC 04/17] nl80211: change __cfg80211_rdev_from_info Johannes Berg
2012-06-19 14:50 ` [RFC 05/17] nl80211: use __cfg80211_rdev_from_attrs for testmode Johannes Berg
2012-06-19 14:50 ` [RFC 06/17] nl80211: prepare for non-netdev wireless devs Johannes Berg
2012-06-25 13:46   ` Eliad Peller
2012-06-25 14:12     ` Johannes Berg [this message]
2012-06-19 14:50 ` [RFC 07/17] nl80211: add NL80211_FLAG_NEED_WDEV Johannes Berg
2012-06-19 14:50 ` [RFC 08/17] nl80211: retrieve interface data by wdev Johannes Berg
2012-06-19 14:50 ` [RFC 09/17] nl80211: don't assume wdev->netdev exists Johannes Berg
2012-06-19 14:50 ` [RFC 10/17] cfg80211: use wdev in some APIs Johannes Berg
2012-06-19 14:50 ` [RFC 11/17] cfg80211: use wireless_dev for interface management Johannes Berg
2012-06-19 14:50 ` [RFC 12/17] nl80211: send interface after creation Johannes Berg
2012-06-19 14:50 ` [RFC 13/17] nl80211: move scan API to wdev Johannes Berg
2012-06-19 16:49   ` Arend van Spriel
2012-06-19 16:53     ` Johannes Berg
2012-06-19 14:50 ` [RFC 14/17] mac80211: remove unused function Johannes Berg
2012-06-19 14:50 ` [RFC 15/17] cfg80211: add P2P Device abstraction Johannes Berg
2012-06-25 15:20   ` Eliad Peller
2012-06-25 15:48     ` Johannes Berg
2012-06-25 16:05       ` Eliad Peller
2012-06-25 16:16         ` Johannes Berg
2012-06-25 17:07           ` Johannes Berg
2012-06-19 14:50 ` [RFC 16/17] mac80211: make ieee80211_check_concurrent_iface netdev-independent Johannes Berg
2012-06-19 14:50 ` [RFC 17/17] mac80211: support P2P Device abstraction Johannes Berg
2012-06-25  8:06 ` [RFC 0/17] add P2P Device support 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=1340633534.27437.2.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=eliad@wizery.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.