From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"John W. Linville" <linville@tuxdriver.com>,
Dave Jones <davej@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: Oops report for the week preceding June 16th, 2008
Date: Tue, 17 Jun 2008 11:20:23 +0200 [thread overview]
Message-ID: <20080617092023.GA20621@elte.hu> (raw)
In-Reply-To: <4856AFDF.5080901@linux.intel.com>
* Arjan van de Ven <arjan@linux.intel.com> wrote:
> This week, a total of 3877 oopses and warnings have been reported,
> compared to 3390 reports in the previous week.
>
> Recently, Fedora put out an updated kernel that contained a wireless
> update; unfortunately, this update was rather broken and caused
> various things to show up in the top 20. A few days later, another
> update fixing the most obvious ones got released with the result that
> only rank 2 and 9 are from the broken update, rather than a lot more..
sidenote: i suspect Fedora has done this to enable more hardware, and/or
to fix mainline wireless bugs?
I wish we would do such new driver merging in mainline instead, so that
we had a single point of testing and single point of effort.
Same for Nouveau: Fedora carries it and i dont understand why such a
major piece of work is not done in mainline and not _helped by_
mainline. It's not like there would be any big risk from having such a
new, experimental 3D driver around - instead of people running nvidia.ko
that causes trouble in all sorts of other subsystems.
All the years of moaning about nvidia.ko and finally we have some real
OSS project and real chance of action but after a year of development
Nouveau still has not been picked up ...
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.
While we dont want to merge anything that gets thrown at us, not merging
new, major, new-hardware-enabling OSS drivers in the mainline kernel is
almost the same thing as intentionally hurting OSS projects and helping
binary-only drivers.
Ingo
next prev parent reply other threads:[~2008-06-17 9:21 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 [this message]
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
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=20080617092023.GA20621@elte.hu \
--to=mingo@elte.hu \
--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=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