From: Matt Domsch <Matt_Domsch@dell.com>
To: Samuel Flory <sflory@rackable.com>
Cc: Brad House <brad_mssw@gentoo.org>,
jgarzik@pobox.com, linux-kernel@vger.kernel.org,
Atul.Mukker@lsil.com
Subject: Re: [PATCH 2.6.0] megaraid 64bit fix/cleanup (AMD64)
Date: Tue, 30 Dec 2003 17:11:43 -0600 [thread overview]
Message-ID: <20031230171143.A23209@lists.us.dell.com> (raw)
In-Reply-To: <3FF1D7EE.5050603@rackable.com>; from sflory@rackable.com on Tue, Dec 30, 2003 at 11:54:22AM -0800
> There is a 2.00.9 in 2.4. In theory you should really be asking on
> linux-megaraid-devel@dell.com.
linux-megaraid-devel@dell.com is closed and gone now (only archives
remain). megaraid driver issues should be discussed on
linux-scsi@vger.kernel.org now. Atul had ported 2.00.6 or so to 2.6
already and posted it to linux-scsi for comment, before the hard
freeze hit; James may have newer code pending somewhere.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2003-12-30 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 5:10 [PATCH 2.6.0] megaraid 64bit fix/cleanup (AMD64) Brad House
2003-12-30 5:20 ` Jeff Garzik
2003-12-30 6:26 ` Brad House
2003-12-30 6:35 ` Jeff Garzik
2003-12-30 19:43 ` Samuel Flory
2003-12-30 19:49 ` Brad House
2003-12-30 19:54 ` Samuel Flory
2003-12-30 21:09 ` Brad House
2003-12-30 23:11 ` Matt Domsch [this message]
[not found] <18kst-5Av-1@gated-at.bofh.it>
2003-12-30 5:26 ` Andi Kleen
2004-01-01 14:08 ` Brad House
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 13:56 Jord Tanner
2004-04-16 16:35 Mukker, Atul
2004-04-16 19:21 ` Jord Tanner
[not found] ` <A1E28594-9478-11D8-B5AA-000A95CD704C@wagland.net>
2004-04-22 18:22 ` Jord Tanner
2004-04-22 18:37 ` Christoph Hellwig
2004-04-16 19:24 Mukker, Atul
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=20031230171143.A23209@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=Atul.Mukker@lsil.com \
--cc=brad_mssw@gentoo.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sflory@rackable.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.