From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@digeo.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: RFC: what's in a stable series?
Date: Wed, 9 Jul 2003 20:54:20 -0700 [thread overview]
Message-ID: <20030710035419.GB32507@kroah.com> (raw)
In-Reply-To: <3F0CBC08.1060201@pobox.com>
On Wed, Jul 09, 2003 at 09:06:16PM -0400, Jeff Garzik wrote:
>
> Does it mean, no API changes except for security (or similarly severe) bugs?
Do that, and we will stagnate.
> Does it mean, no userland ABI changes, but API changes affecting onto
> the kernel are ok?
That sounds acceptable to me.
But maybe I'm just biased, as I'm looking to start backporting some of
the USB 2.5 changes to 2.4 to fix real bugs that are in 2.4. This will
require changing kernel apis. And in doing so, fixing up all of the
in-kernel usages of that api will happen.
In doing this, it just enforces the fact that it really matters if you
have a in-kernel driver or not. If you want to keep a driver or any
other kernel code outside of the main tree, it is costly, both in time
and effort.
My .02
greg k-h
next prev parent reply other threads:[~2003-07-10 3:39 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
2003-07-10 11:22 ` Alan Cox
2003-07-10 12:36 ` Herbert Pötzl
2003-07-10 3:54 ` Greg KH [this message]
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=20030710035419.GB32507@kroah.com \
--to=greg@kroah.com \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@osdl.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