Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268911AbTGJDjq (ORCPT ); Wed, 9 Jul 2003 23:39:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268912AbTGJDjp (ORCPT ); Wed, 9 Jul 2003 23:39:45 -0400 Received: from storm.he.net ([64.71.150.66]:44469 "HELO storm.he.net") by vger.kernel.org with SMTP id S268911AbTGJDjo (ORCPT ); Wed, 9 Jul 2003 23:39:44 -0400 Date: Wed, 9 Jul 2003 20:54:20 -0700 From: Greg KH To: Jeff Garzik Cc: LKML , Marcelo Tosatti , Alan Cox , Andrew Morton , Linus Torvalds Subject: Re: RFC: what's in a stable series? Message-ID: <20030710035419.GB32507@kroah.com> References: <3F0CBC08.1060201@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F0CBC08.1060201@pobox.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1042 Lines: 29 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/