linux-kernel - Re: iwl4965 and driver merging policy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070928023055.GI7991@tuxdriver.com>
Date:	Thu, 27 Sep 2007 22:30:55 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...l.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	tomas.winkler@...el.com
Subject: Re: iwl4965 and driver merging policy

On Fri, Sep 28, 2007 at 11:39:27AM +1000, Benjamin Herrenschmidt wrote:

> Just a little question in the light of the discussion we had at Kernel
> Summit about merging drivers upstream (and here, I strongly agree with
> Linus, hence my message).

You must not have been watching me SPAM netdev for the past two
weeks. :-)

> I just got that new T61 laptop which happens to have an iwl4xxx chip.
> The distro I installed on it (ubuntu) has a driver for it. I suspect
> others do too and most users get it from some random external tree and
> use it.
> 
> Thus my question, why are we about to release 2.6.23 without it ?
> 
> It doesn't seem to pull any depedency nor affect any other external
> piece of code unless I'm missing something, so it's a perfect example of
> what we've been discussing back then: there is just no point not merging
> it at any time right ? :-)

It is queued for 2.6.24.  I'm not even sure it was originally posted
in time for the 2.6.23 merge window, but even if it was there was
a lot of opposition to merging it until fairly recently.  In fact,
I'm sure there are still some wireless developers that are less than
happy about merging it now.

Anyway, coming soon to a kernel near you...

John
-- 
John W. Linville
linville@...driver.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/