From: David Lang <david.lang@digitalinsight.com>
To: Clemens Schwaighofer <cs@tequila.co.jp>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.6-rc2-mm2 + Adaptec I2O
Date: Mon, 26 Apr 2004 22:23:06 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0404262221490.17702@dlang.diginsite.com> (raw)
In-Reply-To: <408DE95F.5010201@tequila.co.jp>
I received a patch that works with 2.6.x x<=4 but it breaks with 2.6.5 so
for now I am sticking with 2.6.4 and hopeing that I don't have to swap out
all these raid controllers.
David Lang
On Tue, 27 Apr 2004, Clemens Schwaighofer wrote:
> Date: Tue, 27 Apr 2004 14:02:23 +0900
> From: Clemens Schwaighofer <cs@tequila.co.jp>
> To: Linux Kernel ML <linux-kernel@vger.kernel.org>
> Subject: 2.6.6-rc2-mm2 + Adaptec I2O
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> oldies but goldies ...
>
> Some old game, same stuff again. Linux-2.6.6-rc2 + mm2 and the adaptec
> i2o is still not compiling. There is a patch swirring around the
> internet for 2.6.5 where the kernel compiles (thought i couldn't reboot
> the box yet, so no "real" expierence).
>
> What is the status? Will there be ever a 2.6.x kernel with a working i2o
> driver? Do I have to blackmail Adaptec ;) ?
>
> lg, clemens
> - --
> Clemens Schwaighofer - IT Engineer & System Administration
> ==========================================================
> TEQUILA\Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
> Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
> http://www.tequila.co.jp
> ==========================================================
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFAjelejBz/yQjBxz8RAickAJ9WpfJvZ/kH0tLPqXP3zSSUlwH4ZwCfZUMw
> usTbWV0xDVrMvZVay7Hq+GQ=
> =vVqS
> -----END PGP SIGNATURE-----
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
next prev parent reply other threads:[~2004-04-27 5:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 5:02 Clemens Schwaighofer
2004-04-27 5:18 ` Andrew Morton
2004-04-27 5:25 ` David Lang
2004-04-27 5:35 ` Clemens Schwaighofer
2004-04-27 6:04 ` Andrew Morton
2004-04-27 6:21 ` Clemens Schwaighofer
2004-04-27 6:25 ` Andrew Morton
2004-04-27 11:53 ` Go Taniguchi
2004-04-27 5:23 ` David Lang [this message]
2004-04-27 5:37 ` Chris Meadors
2004-04-27 5:39 ` Clemens Schwaighofer
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.58.0404262221490.17702@dlang.diginsite.com \
--to=david.lang@digitalinsight.com \
--cc=cs@tequila.co.jp \
--cc=linux-kernel@vger.kernel.org \
/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®