From: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
To: "Miquel van Smoorenburg" <miquels@cistron.nl>,
"Anders Henke" <anders.henke@1und1.de>
Cc: "FUJITA Tomonori" <tomof@acm.org>, <matthew@wil.cx>,
<jack@ucw.cz>, <fujita.tomonori@lab.ntt.co.jp>,
<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>
Subject: RE: broken dpt_i2o in 2.6.23 (was: ext2_check_page: bad entry indirectory) (fwd)
Date: Wed, 12 Dec 2007 08:25:10 -0500 [thread overview]
Message-ID: <AE4F746F2AECFC4DA4AADD66A1DFEF0101052210@otce2k301.adaptec.com> (raw)
In-Reply-To: <1197409983.6288.9.camel@localhost.localdomain>
ACK, patch looks good. Thanks for composing this patch. Glad to hear of
successful test results.
Sincerely -- Mark Salyzyn
> -----Original Message-----
> From: linux-scsi-owner@vger.kernel.org
> [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Miquel
> van Smoorenburg
. . .
>
> I just recompiled 2.6.23.9 with the 64 bit patch for dpt_i2o
> and now it
> boots just fine.
>
> The patch is here:
> http://www.miquels.cistron.nl/linux/dpt_i2o-64bit-2.6.23.patch
>
> It's not the final version - it needs a few cleanups before it can be
> submitted, but perhaps you can test if it also works for you.
>
> Mike.
prev parent reply other threads:[~2007-12-12 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 13:03 broken dpt_i2o in 2.6.23 (was: ext2_check_page: bad entry in directory) (fwd) Jan Kara
2007-11-29 14:55 ` FUJITA Tomonori
2007-11-29 16:45 ` Anders Henke
2007-11-29 17:04 ` Matthew Wilcox
2007-11-30 13:27 ` Anders Henke
2007-11-29 17:09 ` FUJITA Tomonori
2007-11-30 10:34 ` Anders Henke
2007-12-11 14:40 ` Miquel van Smoorenburg
2007-12-11 16:07 ` broken dpt_i2o in 2.6.23 (was: ext2_check_page: bad entry indirectory) (fwd) Salyzyn, Mark
2007-12-11 21:53 ` broken dpt_i2o in 2.6.23 (was: ext2_check_page: bad entry in directory) (fwd) Miquel van Smoorenburg
2007-12-12 13:25 ` Salyzyn, Mark [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=AE4F746F2AECFC4DA4AADD66A1DFEF0101052210@otce2k301.adaptec.com \
--to=mark_salyzyn@adaptec.com \
--cc=anders.henke@1und1.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jack@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=miquels@cistron.nl \
--cc=tomof@acm.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;
as well as URLs for NNTP newsgroup(s).