All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: RFC:  what's in a stable series?
Date: Thu, 10 Jul 2003 08:53:32 +0100	[thread overview]
Message-ID: <20030710085332.B28672@infradead.org> (raw)
In-Reply-To: <20030710033409.GA1498@www.13thfloor.at>; from herbert@13thfloor.at on Thu, Jul 10, 2003 at 05:34:09AM +0200

On Thu, Jul 10, 2003 at 05:34:09AM +0200, Herbert Pötzl wrote:
> In my opinion (and you requested input *g*), the
> kernel userland API can be changed as much as is
> required to improve/stabilize/bugfix the kernel,
> unless this change breaks something in userland
> without an already available update/upgrade/etc ...

Changing the kernel/userland API and ABI is totally out of question - 
we _really_ can't do that.  This is about inkernel APIs for modules.

  reply	other threads:[~2003-07-10  7:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10  1:06 RFC: what's in a stable series? Jeff Garzik
2003-07-10  1:08 ` Jeff Garzik
2003-07-10  3:34 ` Herbert Pötzl
2003-07-10  7:53   ` Christoph Hellwig [this message]
2003-07-10 11:22   ` Alan Cox
2003-07-10 12:36     ` Herbert Pötzl
2003-07-10  3:54 ` Greg KH
2003-07-10  3:54 ` Marcelo Tosatti
2003-07-10  4:16   ` Andrew Morton
2003-07-10  7:53     ` Christoph Hellwig
2003-07-10  8:25       ` Andrew Morton
2003-07-10  7:53   ` Christoph Hellwig
2003-07-10 11:19     ` Alan Cox
2003-07-10 12:13       ` Marcelo Tosatti
2003-07-10 12:42         ` Alan Cox
2003-07-10 15:15           ` Christoph Hellwig
2003-07-10 19:00             ` Jan Kara
2003-07-11  8:36               ` Christoph Hellwig
2003-07-11  9:21             ` Alan Cox
2003-07-10 15:12         ` Christoph Hellwig
2003-07-10 15:11       ` Christoph Hellwig

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=20030710085332.B28672@infradead.org \
    --to=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.