From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: 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 14:51:53 -0700 (PDT) [thread overview]
Message-ID: <20080617.145153.229833994.davem@davemloft.net> (raw)
In-Reply-To: <20080617153356.GA3510@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Tue, 17 Jun 2008 17:33:56 +0200
> v2.6.24 was no doubt a huge step in the right direction but it came too
> late and we are still suffering from the fallout today as we have not
> reached test cycle equilibrium yet: by the time mainline gets the
> patches a new large batch comes up, invalidating much of mainline's role
> and forcing distros to gamble with (much untested and thus detached from
> reality) experimental branches.
>
> That's my main point: when we mess up and dont merge OSS driver code
> that was out there in time - and we messed up big time with wireless -
> we should admit the screwup and swallow the bitter pill.
Your point seems to be that, even though we've acknowledged and
entirely corrected the problem now, you still will whack us over the
head and complain because it took in your opinion too long to get to
that point.
How nice. That makes the wireless folks feel great I imagine.
You also have no idea what infrastructure or other invasive wireless
subsystem changes might have been necessary to merge in some of those
drivers. Of course, that doesn't suit your goal of making the
wireless folks look like a bunch of incompetant twits, so it doesn't
surprise me that you haven't investigated any such facts.
It is impossible, therefore, to please you since we cannot change the
past. So all we can do at this point is continue doing the right
thing and completely ignore your pointless whines.
In this context your complaints are beyond unfair and beyond
pointless, therefore you're finally in my kill file now, have a nice
day Ingo.
next prev parent reply other threads:[~2008-06-17 21:52 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
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 [this message]
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=20080617.145153.229833994.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=davej@redhat.com \
--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
Powered by JetHome