From: Martins Krikis <mkrikis@yahoo.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com,
mkrikis@yahoo.com
Subject: Re: [Announce] "iswraid" (ICH5R/ICH6R ataraid sub-driver) for 2.4.28-pre3
Date: Sat, 9 Oct 2004 19:40:34 -0700 (PDT) [thread overview]
Message-ID: <20041010024034.60520.qmail@web13727.mail.yahoo.com> (raw)
In-Reply-To: <58cb370e041009190678aa4c87@mail.gmail.com>
--- Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> We SHOULD be discouraging new people from
> contributing to DEPRECATED kernel series.
But 2.4 wasn't quite that deprecated when version 0.0.6
of iswraid was announced on Nov 24, 2003. I don't know
the exact 2.6 timeline but ChangeLog-2.6.0 at www.kernel.org
seems to be dated Dec 17, 2003. Yes, perhaps we should
have asked for consideration sooner...
> > Actually, that is not the reason. There is very little
> > dependence on ataraid in iswraid. It would be quite easy
> > to make iswraid a completely standalone driver. It has not
> > been ported to 2.6 primarily because it would not be welcome
>
> not because user-space solution is superior?
Like you said, superior from a maintenance point of view.
The users might choose a different measure for superiority.
The coder doing the work may choose yet another way of
deciding which way to proceed. For example, if time was all
that mattered, I think, it would be faster for me to just make
an iswraid port to 2.6 than to try to work with dm+dmraid
which I know very little about, in order to get the same
features supported. But, because I can't speak for my employer,
let me agree with you here and say that yes, I stand corrected,
it is quite possible that it has not been ported because a user
space solution is superior.
> I'm sorry that I dare to not love iswraid... ;-)
You've made your reasons so clear that I don't really mind.
These opinions are solely mine and
may not agree with those of my employer.
Martins Krikis
next prev parent reply other threads:[~2004-10-10 2:40 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 ` 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
2004-10-10 1:00 ` Martins Krikis
2004-10-10 2:06 ` Bartlomiej Zolnierkiewicz
2004-10-10 2:40 ` Martins Krikis [this message]
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=20041010024034.60520.qmail@web13727.mail.yahoo.com \
--to=mkrikis@yahoo.com \
--cc=bzolnier@gmail.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®