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 for Android: free password hash cracker in your pocket

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

Message-Id: <20080617.145153.229833994.davem@davemloft.net>
Date:	Tue, 17 Jun 2008 14:51:53 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mingo@...e.hu
Cc:	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

From: Ingo Molnar <mingo@...e.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.
--
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/