linux-kernel - Re: Oops report for the week preceding June 16th, 2008

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: <1213730654.3803.122.camel@johannes.berg>
Date:	Tue, 17 Jun 2008 21:24:14 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	David Miller <davem@...emloft.net>, arjan@...ux.intel.com,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, tglx@...utronix.de,
	linville@...driver.com, davej@...hat.com, gregkh@...e.de
Subject: Re: Oops report for the week preceding June 16th, 2008

> i have no gripes about the current situation of wireless in linux-next, 
> other than it all came 1-2 years too late:

Clearly, you don't have a clue about wireless. I'll admit to being
pissed off by statements like this because I personally spent a lot of
time getting wireless code into shape for merging, and it took a long
time.

If we'd have merged the existing wireless drivers 2 years ago, we would
have (at least) four 802.11 stacks in the kernel now, at least two
legally questionable drivers (the ath5k legal situation would probably
never have been cleared up, acx100 still isn't), no uniform API so it
would be impossible to write userspace support tools etc.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)