From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
dcbw@redhat.com, hs4233@mail.mn-solutions.de,
linux-kernel@vger.kernel.org
Subject: Re: libertas (private) ioctls vs. nl80211
Date: Thu, 14 Jun 2007 14:48:33 -0400 [thread overview]
Message-ID: <46718D81.9080402@garzik.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0706141121080.14121@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Thu, 14 Jun 2007, Christoph Hellwig wrote:
>>> I suspect that the probability of your proposal succeeding would be increased
>>> if you could prepare a patch...
>> Here we go:
>
> I don't mind ripping them out, but it makes sense only if people are
> actually signed up to implementing this on a higher layer. As such, I'd
> need to get a sign-off from somebody actually involved in wireless mesh
> stuff etc.
Correct me if I'm wrong, linux-wireless, but AFAIK there has never been
a single post or line of code written for a generic wireless _mesh_
interface.
My general sentiment is -- remove the pointless and iw-duplicated
ioctls, but leave the mesh ones that won't see generic counterparts for
years.
Jeff
next prev parent reply other threads:[~2007-06-14 18:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 17:58 libertas (private) ioctls vs. nl80211 Johannes Berg
2007-06-14 17:09 ` Christoph Hellwig
2007-06-14 17:38 ` Andrew Morton
2007-06-14 18:13 ` Christoph Hellwig
2007-06-14 18:23 ` Linus Torvalds
2007-06-14 18:48 ` Jeff Garzik [this message]
2007-06-14 22:22 ` Dan Williams
2007-06-14 22:31 ` Christoph Hellwig
2007-06-14 22:55 ` Dan Williams
2007-06-14 19:09 ` John W. Linville
2007-06-14 19:56 ` Andrew Morton
2007-06-14 20:08 ` John W. Linville
2007-06-17 4:46 ` Matt Mackall
2007-07-06 15:40 ` Javier Cardona
2007-07-06 16:08 ` Dan Williams
2007-07-10 14:56 ` John W. Linville
2007-07-10 15:18 ` John W. Linville
2007-06-18 17:38 ` Dan Williams
2007-06-18 18:44 ` Christoph Hellwig
2007-06-18 18:57 ` Sam Ravnborg
2007-06-14 20:03 ` Holger Schurig
2007-06-14 22:48 ` Dan Williams
2007-06-15 18:42 ` Dan Williams
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=46718D81.9080402@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=dcbw@redhat.com \
--cc=hch@infradead.org \
--cc=hs4233@mail.mn-solutions.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).