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: <1190948859.6158.62.camel@pasglop>
Date:	Fri, 28 Sep 2007 13:07:39 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Theodore Tso <tytso@....edu>
Cc:	"John W. Linville" <linville@...driver.com>,
	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


> 
> Well, pulling in iwlwifi would require also pulling in the mac80211
> subsystem, so it's not quite that simple (although I'm not sure what's
> holding back that going into the kernel.)

I though that was already in 2.6.23 ... my bad if I missed something
(there is definitely something there called net/mac80211)

> I had no problem building my personal production kernel by taking
> 2.6.23-rc8, and doing a git pull from the everything branch in John
> Linville's wireless-dev git tree.  It's probably too late to pull it
> for 2.6.23-rc8 (although if Linux wanted to do it it's only one git
> pull command away :-), but it would be really nice if it could get
> merged in for 2.6.24.

Yes, I agree -rc8 seems to be a tad too late, I'm just surprised we
didn't get it in earlier though since it seems it's been around and
useable for some time.

Cheers,
Ben.


-
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/