From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: syn uw <syn_uw@hotmail.com>
Cc: xose@wanadoo.es, <linux-kernel@vger.kernel.org>,
<marcelo.tosatti@cyclades.com.br>, <atulm@lsil.com>,
<linux-megaraid-devel@dell.com>
Subject: RE: Megaraid does not work with 2.4.22
Date: Wed, 1 Oct 2003 10:21:16 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44.0310011017440.3343-100000@dmt.cyclades> (raw)
In-Reply-To: <BAY99-F60MLDthODt9C000008de@hotmail.com>
On Wed, 1 Oct 2003, syn uw wrote:
> >I don't know what is the opinion of other people :-?
> >Maybe linux-scsi members hold other opinion.
>
> Well I for example would be more than pleased to see megaraid 2.x included
> in the next stable 2.4.x Linux kernel !! I had a look at the current
> changelogs of 2.4.23 and still no traces about a megaraid v2 inclusion :((
> Hopefully that will happen soon !
Having two drivers for the same controller is not a good thing from a user
point of view. I just asked Atul privately but will do so again here: Why
do we need "megaraid2" ?
next prev parent reply other threads:[~2003-10-01 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 11:01 Megaraid does not work with 2.4.22 syn uw
2003-10-01 13:21 ` Marcelo Tosatti [this message]
2003-10-01 15:23 ` Xose Vazquez Perez
2003-10-01 16:08 ` Marcelo Tosatti
2003-10-07 17:44 ` Xose Vazquez Perez
2003-10-08 0:51 ` Marcelo Tosatti
2003-10-08 1:09 ` Xose Vazquez Perez
2003-10-08 1:49 ` Erik Andersen
2003-10-08 10:27 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2003-10-01 23:33 Tomita, Haruo
2003-10-01 21:40 syn uw
2003-10-01 0:11 Tomita, Haruo
2003-09-30 19:34 Matt_Domsch
2003-09-30 19:21 Xose Vazquez Perez
[not found] <0E3FA95632D6D047BA649F95DAB60E570185F531@exa-atlanta.se.lsil.com>
2003-09-26 9:07 ` Marcelo Tosatti
2003-08-28 11:08 Krzysztof Olędzki
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=Pine.LNX.4.44.0310011017440.3343-100000@dmt.cyclades \
--to=marcelo.tosatti@cyclades.com \
--cc=atulm@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-megaraid-devel@dell.com \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=syn_uw@hotmail.com \
--cc=xose@wanadoo.es \
/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;
as well as URLs for NNTP newsgroup(s).