From: Marcel Holtmann <marcel@holtmann.org>
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 20:14:55 +0200 [thread overview]
Message-ID: <1240164895.11795.70.camel@violet> (raw)
In-Reply-To: <20090419180314.23710@gmx.net>
Hi Alina,
> > you argue command line tools against kernel exposed API.
>
> I use the command line syntax to explain the kernel API.
and that is just plain wrong to begin with. If you want a one command do
everything, then do that in userspace and not inside a kernel API.
> > Both have
> > nothing to do with each other on that level.
>
> Most commands are mapped 1:1. And the API easier to understand if it is so.
That just happen to be this way right now. It doesn't have to stay that
way and if it would, that would be actually be stupid.
> > If you don't like the iw
> > syntax then fix it and provide a command that does all three task for
> > you. No need to mess with the kernel interface for that.
>
> I think now, provide a high-level command besides the low-level commands is a good idea. We need it for the old wext interface anyway. Then wext can only call this command and don't need own intelligence. So than it's only a foolish wrapper, like it should.
>From my point of view, WEXT can die right now. Just doing something to
make WEXT happy is wrong. If you want something like that then do it in
userspace. I just don't see the need here for an extra kernel API.
Regards
Marcel
next prev parent reply other threads:[~2009-04-19 18:15 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
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 [this message]
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=1240164895.11795.70.camel@violet \
--to=marcel@holtmann.org \
--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).