public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Martins Krikis <mkrikis@yahoo.com>,
	linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29
Date: Mon, 7 Feb 2005 14:45:35 -0200	[thread overview]
Message-ID: <20050207164535.GA5378@logos.cnet> (raw)
In-Reply-To: <1107701373.22680.115.camel@laptopd505.fenrus.org>

On Sun, Feb 06, 2005 at 03:49:33PM +0100, Arjan van de Ven wrote:
> 
> > I consider it not a new feature, but a missing feature, since otherwise 
> > user data cannot be accessed in the RAID setups.
> 
> the same is true for all new hardware drivers and hardware support
> patches. And for new DRM (since new X may need it) and new .. and
> new ... where is the line?
> 
> for me a deep maintenance mode is about keeping existing stuff working;
> all new hw support and derivative hardware support (such as this) can be
> pointed at the new stable series... which has been out for quite some
> time now..

I personally dislike and discourage the addition of ANY new drivers to v2.4 at
this point, and I sincerely appreciate every argument against iswraid, but I 
have no problems with it because it looks like a valid special case since it 
allows users to access their ICH5/6 RAID partitions, as Jeff mentions.

Moreover the driver is going to die with v2.4 anyway, its not like any future 
compatibility problem is being introduced.

So I understand the argument against having it in the tree: the elegant way of doing
it is to use dmraid. 

But I dont buy it as an argument against merging it in a dying v2.4.x tree which 
purpose is to serve existing users. 

You are mistaken in arguing that "oh, since this driver can be merged, its likely that 
any v2.6 HW support/driver will be accepted in v2.4".

So, its up to Jeff, and he seems to be OK with it.

  parent reply	other threads:[~2005-02-07 20:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29  1:15 [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29 Martins Krikis
2005-02-06  2:36 ` Jeff Garzik
2005-02-06  9:27   ` Arjan van de Ven
2005-02-06 12:45     ` Bartlomiej Zolnierkiewicz
2005-02-06 14:38       ` Jeff Garzik
2005-02-06 14:48         ` Christoph Hellwig
2005-02-06 14:49         ` Arjan van de Ven
2005-02-06 15:03           ` Jeff Garzik
2005-02-06 15:19             ` Bartlomiej Zolnierkiewicz
2005-02-10 19:35               ` Bill Davidsen
2005-02-10 20:05                 ` Bartlomiej Zolnierkiewicz
2005-02-10 22:04                   ` Bartlomiej Zolnierkiewicz
2005-02-10 18:39                     ` Marcelo Tosatti
2005-02-10 23:28                       ` Bartlomiej Zolnierkiewicz
2005-02-10 20:33                         ` Marcelo Tosatti
2005-02-11 10:46                       ` Arjan van de Ven
2005-02-06 15:28             ` Arjan van de Ven
2005-02-06 15:50             ` Christoph Hellwig
2005-02-06 16:09               ` Jeff Garzik
2005-02-06 16:27                 ` Christoph Hellwig
2005-02-07 16:45           ` Marcelo Tosatti [this message]
2005-02-07 18:29           ` Martins Krikis
     [not found]             ` <bc8bcc5105020711081f1de175@mail.gmail.com>
2005-02-07 19:30               ` 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=20050207164535.GA5378@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=bzolnier@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --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