mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Greg KH <gregkh@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, 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
Subject: Re: Oops report for the week preceding June 16th, 2008
Date: Tue, 17 Jun 2008 14:43:02 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.1.00.0806171428320.19665@iabervon.org> (raw)
In-Reply-To: <20080617175414.GA9866@suse.de>

On Tue, 17 Jun 2008, Greg KH wrote:

> On Tue, Jun 17, 2008 at 05:33:56PM +0200, Ingo Molnar wrote:
> > IMO we are not learning and are repeating history once again, as the 
> > Nouveau situation is building up towards a similar "we didnt merge it in 
> > time" pain point. From kernel-2.6.25.6-24.fc8.src.rpm:
> > 
> >   -rw-r--r-- 1 root root 513639 2008-05-22 04:31 nouveau-drm.patch
> > 
> >   39 files changed, 13960 insertions(+), 5 deletions(-)
> > 
> > Nouveau has been started in 2006, about two years ago. It's a lot less 
> > painful (not the least it is a lot faster as well) if such things are 
> > developed gradually in mainline.
> 
> Not to dispute your original claim of wanting to merge drivers earlier,
> but a lot of the time, there are good reasons why the code doesn't get
> merged.
> 
> As recently pointed out by the nouveau driver authors on the xorg
> mailing list, they don't want the driver to be added to the main
> kernel.org tree yet as they feel that their userspace/kernelspace
> inteface is not complete and will change in the future.

That's the same reason the wireless drivers didn't get merged sooner, with 
the slight difference that they were waiting on the new 802.11 stack's 
interface to stabilize, rather than their own interface.

On the other hand, it would be good if there were a way to include 
unstable APIs in the mainline kernel so that they could get some exposure 
before they're set in stone, and that would also eliminate that reason for 
keeping drivers out so long.

	-Daniel
*This .sig left intentionally blank*

  parent reply	other threads:[~2008-06-17 18:43 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 [this message]
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=alpine.LNX.1.00.0806171428320.19665@iabervon.org \
    --to=barkalow@iabervon.org \
    --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®