From: dalecki <dalecki@evision-ventures.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] megaraid driver update for 2.4.0-test10
Date: Sun, 19 Nov 2000 18:06:32 +0100 [thread overview]
Message-ID: <3A180898.EB386DB8@evision-ventures.com> (raw)
In-Reply-To: <3A170A06.934405FC@evision-ventures.com> <8v7bm0$hm5$1@enterprise.cistron.net>
Miquel van Smoorenburg wrote:
>
> In article <3A170A06.934405FC@evision-ventures.com>,
> dalecki <dalecki@evision-ventures.com> wrote:
> >This is a multi-part message in MIME format.
> >1. Merge the most current version (aka: 1.08) of the
> > MegaRAID driver from AMI in to the most current kernel
> > (2.4.0-test10 and friends).
>
> The latest is 1.11a or something. The 1.08 one has *bugs*.
> At least if it's the same from the 2.2.18preX series. And even
> that one has still patches outstanding because it doesn't work
No it's not taken from 2.2.18. It's based on the latest stuff found
on www.ami.com. And then I have fixed some issues which where
directly obvious. And then it's not quite broken since it's working
quite fine on the box found here. Anyway. There is some point
where one has to start at ;-).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-19 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 23:00 [PATCH] megaraid driver update for 2.4.0-test10 dalecki
2000-11-18 22:27 ` Jeff Garzik
2000-11-19 17:02 ` dalecki
2000-11-19 1:50 ` Miquel van Smoorenburg
2000-11-19 17:06 ` dalecki [this message]
2000-11-19 21:28 ` Jes Sorensen
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=3A180898.EB386DB8@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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