public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Martins Krikis <mkrikis@yahoo.com>,
	linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com
Subject: Re: [Announce] "iswraid" (ICH5R/ICH6R ataraid sub-driver) for 2.4.28-pre3
Date: Sat, 09 Oct 2004 19:54:20 -0400	[thread overview]
Message-ID: <41687A2C.9000406@pobox.com> (raw)
In-Reply-To: <58cb370e04100916441c1b74d@mail.gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> On Sat, 9 Oct 2004 16:03:00 -0700 (PDT), Martins Krikis
> <mkrikis@yahoo.com> wrote:
> 
>>--- Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl> wrote:
>>
>>
>>>I may sound like an ignorant but...
>>>
>>>Why can't device mapper be merged into 2.4 instead?
>>
>>"Instead" is the key word here... That would mean that
>>Boji's and my work has been largely in vain and that the
>>driver that to my best knowledge currently provides the
>>simplest (from a user's point of view) cooperation with
>>Intel RAID OROM and the most comlete feature-set regarding
>>Intel RAID metadata interpretation and updates would not
>>make it to the kernel. I have nothing against device mapper
>>being merged into 2.4 but I don't consider that a fair
>>reason for not considering iswraid.
> 
> 
> Well, in some way this speaks against merging iswraid in 2.4.
> If it provides "the most comlete feature-set regarding Intel RAID
> metadata interpretation and updates" then merging it would
> create regression when compared to 2.6, wouldn't it?


When the other RAIDs are ataraid in 2.4 and DM in 2.6, doing iswraid DM 
in 2.4 violates the Principle of Least Surprise ;-)

	Jeff



  reply	other threads:[~2004-10-09 23:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87d5zzfds7.fsf@yahoo.com>
2004-10-09 20:44 ` [Announce] "iswraid" (ICH5R/ICH6R ataraid sub-driver) for 2.4.28-pre3 Martins Krikis
2004-10-09 21:37   ` Bartlomiej Zolnierkiewicz
2004-10-09 22:07     ` Jeff Garzik
2004-10-09 23:22       ` Bartlomiej Zolnierkiewicz
2004-10-09 23:36         ` Jeff Garzik
2004-10-09 23:50           ` Bartlomiej Zolnierkiewicz
2004-10-11 11:19             ` Marcelo Tosatti
2004-10-12 14:56               ` Martins Krikis
2005-01-18 17:28               ` iswraid and 2.4.x? Martins Krikis
2005-01-18 15:05                 ` Marcelo Tosatti
2005-01-18 18:13                 ` Jeff Garzik
2005-01-18 15:13                   ` Marcelo Tosatti
2005-01-18 18:34                     ` Jeff Garzik
2005-01-18 19:56                       ` Martins Krikis
2005-01-18 20:55                         ` Bartlomiej Zolnierkiewicz
2005-01-18 21:14                           ` Jeff Garzik
2005-01-18 21:17                             ` Bartlomiej Zolnierkiewicz
2005-01-18 21:59                           ` Martins Krikis
2004-10-09 23:03     ` [Announce] "iswraid" (ICH5R/ICH6R ataraid sub-driver) for 2.4.28-pre3 Martins Krikis
2004-10-09 23:44       ` Bartlomiej Zolnierkiewicz
2004-10-09 23:54         ` Jeff Garzik [this message]
2004-10-10  1:00         ` Martins Krikis
2004-10-10  2:06           ` Bartlomiej Zolnierkiewicz
2004-10-10  2:40             ` Martins Krikis
2004-10-10 18:19   ` Alan Cox
     [not found] <bc8bcc5104100918206842d6d3@mail.gmail.com>
2004-10-10  2:08 ` Martins Krikis

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=41687A2C.9000406@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=mkrikis@yahoo.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