The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Daniel Barkalow <barkalow@iabervon.org>
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 15:48:56 -0700	[thread overview]
Message-ID: <20080617224856.GA16933@suse.de> (raw)
In-Reply-To: <alpine.LNX.1.00.0806171428320.19665@iabervon.org>

On Tue, Jun 17, 2008 at 02:43:02PM -0400, Daniel Barkalow wrote:
> 
> 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.

That's exactly what the documentation in Documentation/ABI is there for.
Document your "experimental" API, along with any userspace programs that
are using it, and work to try to finalize it.

thanks,

greg k-h

  parent reply	other threads:[~2008-06-17 22:51 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
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 [this message]
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=20080617224856.GA16933@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=barkalow@iabervon.org \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --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