From: Johannes Berg <johannes@sipsolutions.net>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Dan Williams <dcbw@redhat.com>
Subject: Re: [RFC] libertas: minimal WEXT handler for MESH
Date: Mon, 26 Oct 2009 17:35:08 +0100 [thread overview]
Message-ID: <1256574908.12462.15.camel@johannes.local> (raw)
In-Reply-To: <200910261729.36583.hs4233@mail.mn-solutions.de>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
On Mon, 2009-10-26 at 17:29 +0100, Holger Schurig wrote:
> For many handlers, I simply put NULL there, but I guess
> that I should do this:
>
> a) register mesh_dev with cfg80211 as well
> b) use the handlers from compat-wext.c instead
>
> Is this right? And I guess that I connot do b) without a)
>
> Or is it ok to do b) without a).
No, it's not, it'll most certainly segfault.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-10-26 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 16:29 [RFC] libertas: minimal WEXT handler for MESH Holger Schurig
2009-10-26 16:35 ` Johannes Berg [this message]
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=1256574908.12462.15.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--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