From: Johannes Berg <johannes@sipsolutions.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: David Miller <davem@davemloft.net>,
arjan@linux.intel.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
tglx@linutronix.de, linville@tuxdriver.com, davej@redhat.com,
gregkh@suse.de
Subject: Re: Oops report for the week preceding June 16th, 2008
Date: Tue, 17 Jun 2008 21:24:14 +0200 [thread overview]
Message-ID: <1213730654.3803.122.camel@johannes.berg> (raw)
In-Reply-To: <20080617153356.GA3510@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
> 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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-06-17 19:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 18:24 Arjan van de Ven
2008-06-17 9:20 ` Ingo Molnar
2008-06-17 9:26 ` David Miller
2008-06-17 15:33 ` Ingo Molnar
2008-06-17 17:54 ` Greg KH
2008-06-17 18:14 ` Dave Jones
2008-06-17 18:43 ` Daniel Barkalow
2008-06-17 19:31 ` Johannes Berg
2008-06-17 22:48 ` Greg KH
2008-06-18 2:40 ` Daniel Barkalow
2008-06-17 19:24 ` Johannes Berg [this message]
2008-06-17 19:41 ` Dave Jones
2008-06-18 3:34 ` Arjan van de Ven
2008-06-18 7:17 ` Johannes Berg
2008-06-18 14:22 ` Arjan van de Ven
2008-06-23 16:55 ` John W. Linville
2008-06-17 21:51 ` David Miller
2008-06-19 0:21 ` Ingo Molnar
2008-06-20 6:01 ` Len Brown
2008-06-17 17:18 ` Bob Copeland
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=1213730654.3803.122.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®