public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hubert Mantel <mantel@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Change of policy for future 2.2 driver submissions
Date: Tue, 9 Jan 2001 15:49:08 +0100	[thread overview]
Message-ID: <20010109154908.F20539@suse.de> (raw)
In-Reply-To: <3A55447D.995FB159@goingware.com> <9350df$2md$1@penguin.transmeta.com>
In-Reply-To: <9350df$2md$1@penguin.transmeta.com>; from torvalds@transmeta.com on Fri, Jan 05, 2001 at 09:31:27AM -0800

Hi,

On Fri, Jan 05, Linus Torvalds wrote:

[...]

> But that's very different from having somebody like RedHat, SuSE or
> Debian make such a kernel part of their standard package. No, I don't
> expect that they'll switch over completely immediately: that would show
> a lack of good judgement. The prudent approach has always been to have
> both a 2.2.19 and a 2.4.0 kernel on there, and ask the user if he wants
> to test the new kernel first.

Right, but now there is a problem: Software RAID. The RAID code of 2.4.0
is not backwards compatible to the one in 2.2.18; if somebody has used
2.4.0 on softraid and discovers some problem, he can not switch back to
some official 2.2 kernel. In order to make it possible to switch between
kernel releases, every vendor now really is forced to integrate the new
RAID0.90 code to their 2.2 kernel. IMHO this code should be integrated to
the next official 2.2 kernel so people can use whatever they want.

> 		Linus
                                                                  -o)
    Hubert Mantel              Goodbye, dots...                   /\\
                                                                 _\_v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-09 14:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05  3:50 Change of policy for future 2.2 driver submissions Michael D. Crawford
2001-01-05  8:29 ` Miles Lane
2001-01-05 17:31 ` Linus Torvalds
2001-01-09 14:49   ` Hubert Mantel [this message]
2001-01-09 14:54     ` Alan Cox
2001-01-09 23:49       ` Jakob Østergaard
2001-01-10  0:02         ` Linus Torvalds
2001-01-10  0:33     ` Ingo Molnar
2001-01-10  1:03       ` Andrea Arcangeli
2001-01-10  1:17         ` Ingo Molnar
2001-01-10  1:40           ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:36 Wayne.Brown
2001-01-08  4:52 Wayne.Brown
2001-01-08 11:07 ` David Weinehall
2001-01-05 20:33 Wayne.Brown
2001-01-06 10:15 ` Nick Holloway
2001-01-05 17:32 Wayne.Brown
2001-01-05 18:50 ` Matthew D. Pitts
2001-01-05 17:11 Wayne.Brown
2001-01-05 17:15 ` Alan Cox
2001-01-05 17:23   ` Christoph.Hellwig.
     [not found]     ` <hchÀcaldera.de>
2001-01-05 17:31       ` Alan Cox
2001-01-05  2:41 Alan Cox
2001-01-05  3:27 ` Nicholas Knight
2001-01-05  4:23   ` Mark Hahn
2001-01-05 12:52     ` Daniel Phillips
2001-01-05  6:38   ` Tim Riker
2001-01-05  6:57   ` Andre Tomt
2001-01-05  7:30     ` Gerhard Mack
2001-01-05 11:46   ` Rik van Riel

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=20010109154908.F20539@suse.de \
    --to=mantel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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