From: "John W. Linville" <linville@tuxdriver.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
tomas.winkler@intel.com
Subject: Re: iwl4965 and driver merging policy
Date: Fri, 28 Sep 2007 09:28:47 -0400 [thread overview]
Message-ID: <20070928132847.GA4989@tuxdriver.com> (raw)
In-Reply-To: <1190949323.6158.66.camel@pasglop>
On Fri, Sep 28, 2007 at 01:15:23PM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2007-09-27 at 22:30 -0400, John W. Linville wrote:
> > I'm sure there are still some wireless developers that are less than
> > happy about merging it now.
> Out of curiosity, what's the main source of opposition ? Since it's
> being shipped by distro or built out of tree by most users -anyway-, I
> think it's pretty clear that we'd be better off having it merged asap
> rather than trying to figure out what random version was included by
> users/distros and try to support it, in addition to wider exposure & all
> the yadada of being upstream in the first place.
There have been a lot of spats about how functionality has been
partitioned between the driver and the firmware, issues with how the
driver tries to do things that either ought to be in mac80211 or not
done at all, and some random complaints about ugliness like '#include
"../../../net/mac80211/blah.h"', etc. There is still plenty of work
to be done on this driver, but as you point out we are better-off
with it in the kernel than with it out.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-09-28 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 1:39 iwl4965 and driver merging policy Benjamin Herrenschmidt
2007-09-28 2:30 ` John W. Linville
2007-09-28 3:15 ` Benjamin Herrenschmidt
2007-09-28 13:28 ` John W. Linville [this message]
2007-09-28 2:47 ` Theodore Tso
2007-09-28 3:07 ` Benjamin Herrenschmidt
2007-10-01 8:24 ` Jiri Kosina
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=20070928132847.GA4989@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--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