From: Johannes Berg <johannes@sipsolutions.net>
To: Alina Friedrichsen <x-alina@gmx.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT v2] cfg80211/nl80211: add IBSS API
Date: Sun, 19 Apr 2009 15:41:58 +0200 [thread overview]
Message-ID: <1240148519.898.3.camel@johannes.local> (raw)
In-Reply-To: <20090419133544.158820@gmx.net> (sfid-20090419_153615_967882_D1A9F951)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On Sun, 2009-04-19 at 15:35 +0200, Alina Friedrichsen wrote:
> Hello Johannes!
>
> > Because you don't associate with an IBSS?
>
> This is only a name, but the call does mostly the same. I think having
> one generic API goes more along with the UNIX philosophy, than having
> for each mode a defend API, on which almost only the names of the
> calls are deferent.
Huh? No, it does not mostly do the same. Quite not so. Managed and IBSS
modes are _really_ different. Almost the only thing they have in common
is that they use an SSID and a BSSID.
And an airy concept of "UNIX philosophy" really has nothing whatsoever
to do with it.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-19 13:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 22:49 [RFC/RFT] cfg80211/nl80211: add IBSS API Johannes Berg
2009-04-18 23:37 ` [RFC/RFT v2] " Johannes Berg
2009-04-19 12:52 ` Alina Friedrichsen
2009-04-19 13:17 ` Johannes Berg
2009-04-19 13:35 ` Alina Friedrichsen
2009-04-19 13:41 ` Johannes Berg [this message]
2009-04-19 14:05 ` Alina Friedrichsen
2009-04-19 14:11 ` Johannes Berg
2009-04-19 15:16 ` Alina Friedrichsen
2009-04-19 15:25 ` Johannes Berg
2009-04-19 15:53 ` Alina Friedrichsen
2009-04-19 15:57 ` Johannes Berg
2009-04-19 16:13 ` Alina Friedrichsen
2009-04-19 16:26 ` Johannes Berg
2009-04-19 16:54 ` Alina Friedrichsen
2009-04-19 16:57 ` Johannes Berg
2009-04-19 17:33 ` Alina Friedrichsen
2009-04-19 17:49 ` Marcel Holtmann
2009-04-19 18:03 ` Alina Friedrichsen
2009-04-19 18:14 ` Marcel Holtmann
2009-04-19 18:43 ` Alina Friedrichsen
2009-04-19 18:55 ` Johannes Berg
2009-04-19 19:01 ` Alina Friedrichsen
2009-04-19 19:21 ` Johannes Berg
2009-04-19 19:25 ` Alina Friedrichsen
2009-04-19 19:31 ` Marcel Holtmann
2009-04-19 19:52 ` Alina Friedrichsen
2009-04-19 19:31 ` Marcel Holtmann
2009-04-19 19:40 ` Johannes Berg
2009-04-19 13:22 ` [RFC/RFT] " Johannes Berg
2009-04-19 14:33 ` Alina Friedrichsen
2009-04-19 16:32 ` Alina Friedrichsen
2009-04-19 16:54 ` Johannes Berg
2009-04-19 17:15 ` Alina Friedrichsen
2009-04-19 17:19 ` Johannes Berg
2009-04-19 17:45 ` Alina Friedrichsen
2009-04-19 18:00 ` Johannes Berg
2009-04-19 18:18 ` Alina Friedrichsen
2009-04-19 18:34 ` Johannes Berg
2009-04-19 18:42 ` Alina Friedrichsen
[not found] ` <20090419142631.158790@gmx.net>
2009-04-19 14:33 ` Johannes Berg
2009-04-19 14:37 ` Johannes Berg
2009-04-19 14:49 ` Alina Friedrichsen
[not found] ` <1240151561.898.12.camel@johannes.local>
2009-04-19 14:41 ` Alina Friedrichsen
2009-04-19 14:53 ` 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=1240148519.898.3.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).