From: Martins Krikis <mkrikis@yahoo.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Martins Krikis <mkrikis@yahoo.com>,
marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29
Date: Mon, 7 Feb 2005 10:29:21 -0800 (PST) [thread overview]
Message-ID: <20050207182921.3015.qmail@web30206.mail.mud.yahoo.com> (raw)
In-Reply-To: <1107701373.22680.115.camel@laptopd505.fenrus.org>
--- Arjan van de Ven <arjan@infradead.org> 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..
Would it help my case if I swore that iswraid has been released
for longer than the "new stable series" and that it is in "deep
maintenance mode" itself, just outside the 2.4 kernel tree?
(Version 0.0.6 (for 2.4.22) was announced Nov. 24, 2003.)
I do realize that Intel should have asked a long time ago for it
to be considered for acceptance (I did ask back in October for
2.4.28). But there are positive aspects to accepting a driver
late---there is a much higher chance that all the issues have
been solved. (If there are any particular worries about the
newly added RAID1E code, well, it's only useful for ICH7R, I'd
be almost as happy if an older version without it got accepted.)
To conclude, Marcelo's words back in October 9 were:
"New drivers are OK, as long as they don't break existing setups,
and if substantial amount of users will benefit from it."
So here is a "new driver" (that's been around for a while)
which I don't think can break anything. As to the "substantial
amount of users", the two SourceForge releases with download
statistics have each seen about 800 downloads, I have no idea
whether that counts as substantial.
Martins Krikis
Storage Components Division
Intel Massachusetts
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
next prev parent reply other threads:[~2005-02-07 18:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 1:15 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
2005-02-07 18:29 ` Martins Krikis [this message]
[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=20050207182921.3015.qmail@web30206.mail.mud.yahoo.com \
--to=mkrikis@yahoo.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=marcelo.tosatti@cyclades.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
all inboxes | Powered by JetHome®