From: Matt Mackall <mpm@selenic.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
dcbw@redhat.com, hs4233@mail.mn-solutions.de,
linux-kernel@vger.kernel.org, marcelo@kvack.org
Subject: Re: libertas (private) ioctls vs. nl80211
Date: Sat, 16 Jun 2007 23:46:36 -0500 [thread overview]
Message-ID: <20070617044636.GL11166@waste.org> (raw)
In-Reply-To: <20070614200844.GC28917@tuxdriver.com>
On Thu, Jun 14, 2007 at 04:08:44PM -0400, John W. Linville wrote:
> On Thu, Jun 14, 2007 at 12:56:18PM -0700, Andrew Morton wrote:
> > On Thu, 14 Jun 2007 15:09:36 -0400
> > "John W. Linville" <linville@tuxdriver.com> wrote:
> >
> > > It does not make sense to me to rip this out purely for aesthetic
> > > reasons.
> >
> > Aesthetics are good, but that's not the main issue.
> >
> > What is most worrying is that there appears to be a risk that these
> > newly-added interfaces will later become obsoleted by another interface.
> > This means that we'll need to maintain, test and support _both_ interfaces
> > for a very long time. This is the sort of foot-shooting we should avoid.
>
> True enough. However, I hope you will agree that we should not
> confuse foresight with speculation.
>
> At present there is no sign on the horizon of either any mac80211
> mesh code or any other full-MAC wireless driver supporting mesh.
> Without either of those, it would seem imprudent to rush toward
> a gneric configuration interface even if nl80211 was prepared to
> sprout one.
Making it generic may be premature optimization.
But at the very least, we should deal with the three other problems
Christoph has pointed out: subfunctions, pointer indirections, and
32on64 cleanliness.
That last one may come back to bite you in a couple years' time, if not
other people. It's a major pain in the ass.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2007-06-17 4:47 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
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 [this message]
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=20070617044636.GL11166@waste.org \
--to=mpm@selenic.com \
--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=linville@tuxdriver.com \
--cc=marcelo@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.