From: Johannes Berg <johannes@sipsolutions.net>
To: Alina Friedrichsen <x-alina@gmx.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 1/2] mac80211: don't add BSS when creating IBSS
Date: Fri, 06 Feb 2009 21:43:04 +0100 [thread overview]
Message-ID: <1233952984.4175.25.camel@johannes.local> (raw)
In-Reply-To: <20090206190012.260110@gmx.net> (sfid-20090206_200044_110756_7814C10D)
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On Fri, 2009-02-06 at 20:00 +0100, Alina Friedrichsen wrote:
> Hello Johannes!
>
> > Tested both together with IBSS, works fine. Haven't tested fixed channel
> > and/or fixed BSSID though.
>
> I have tested both, it works fine, too. :)
Thanks Alina, I'll have to split up the second patch (cfg80211 changes)
and look at the function naming you suggested, and then repost in a few
days as [PATCH]
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-02-06 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 10:58 [RFC 1/2] mac80211: don't add BSS when creating IBSS Johannes Berg
2009-02-06 14:42 ` Johannes Berg
2009-02-06 19:00 ` Alina Friedrichsen
2009-02-06 20:43 ` 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=1233952984.4175.25.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=x-alina@gmx.net \
/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).