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 02:26:52 -0700 (PDT) [thread overview]
Message-ID: <20080617.022652.76635616.davem@davemloft.net> (raw)
In-Reply-To: <20080617092023.GA20621@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Tue, 17 Jun 2008 11:20:23 +0200
> When distros feel the need to add large and risky patches that IMO shows
> process failure on our part and further isolates mainline from distros
> and from testers.
You say this to the point where you sound like a broken record. It's
a bit tiring, and nothing positive ever comes of these rants.
And I think you massively oversimplify the situation, to top it
off.
On the wireless front, I severely doubt... in fact I know because I'm
looking at every wireless merge going into my tree, that John Linville
is not holding back new drivers submissions from the current 2.6.26
tree. Neither is Jeff Garzik for non-wireless net drivers.
If the Fedora9 tree is based off of 2.6.25 or similar (it is), well
that's how life works. Stuff gets backported from mainline into
whatever they are using and stuff breaks from time to time.
Did you investigate any of these facts to figure out what the specific
situation is here? Or did some of your favorite keywords pop up Arjan's
report so that you could unleash your favorite whine?
next prev parent reply other threads:[~2008-06-17 9:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 18:24 Oops report for the week preceding June 16th, 2008 Arjan van de Ven
2008-06-17 9:20 ` Ingo Molnar
2008-06-17 9:26 ` David Miller [this message]
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
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.022652.76635616.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