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: 07 Feb 2005 14:30:47 -0500 [thread overview]
Message-ID: <87d5vc9nh4.fsf_-_@yahoo.com> (raw)
In-Reply-To: <bc8bcc5105020711081f1de175@mail.gmail.com>
Martins Krikis <mkrikis@yahoo.com> writes:
> 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).
Sorry about all the noise, but I just remembered some other important
aspects that played a role here.
Intel couldn't really ask for the inclusion of iswraid into the tree
much earlier than October because iswraid depends on either ata_piix
or ahci, both part of libata. Libata was included in 2.4.27, ata_piix
in 2.4.28, ahci in 2.4.29.
So I first asked for iswraid to be considered during 2.4.28-pre3 stage.
I was told that it's almost being released and that I should wait
for 2.4.29. There was also a discussion about whether it even belongs
or whether dm belongs more. With 2.4.29 I forgot to remind everybody
to look at iswraid and when I did it was too late for 2.4.29 and
Marcelo asked Jeff to review it for 2.4.30-pre1. (And thanks for
your support, Jeff.)
In short, I only first asked for it to be included with 2.4.28, but
I could not have done it earlier than that anyway because drivers it
depends on weren't yet in 2.4.
Martins Krikis
Storage Components Division
Intel Massachusetts
prev parent reply other threads:[~2005-02-07 19:32 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
2005-02-07 18:29 ` Martins Krikis
[not found] ` <bc8bcc5105020711081f1de175@mail.gmail.com>
2005-02-07 19:30 ` Martins Krikis [this message]
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=87d5vc9nh4.fsf_-_@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.