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: Tue, 11 Dec 2007 11:07:08 -0500 [thread overview]
Message-ID: <AE4F746F2AECFC4DA4AADD66A1DFEF0101052133@otce2k301.adaptec.com> (raw)
In-Reply-To: <1197384034.19679.13.camel@n2o.xs4all.nl>
Miquel van Smoorenburg sez:
> I got the 64-bit dpt_i2o driver from Adaptec some time ago, and I have
> added 64-bit support to the 2.6.23.1 dpt_i2o driver based on that
> driver. I intended to submit it for 2.6.25 or so ... if I
> have some time
> later today or tomorrow I'll try that next to see if that makes a
> difference.
Thanks, Mike, I will be watching your progress and offer my support! I
submitted a patch to move to 64 bit (which also drops the virt_to_bus
code) several years ago and it was rejected because of the focus on the
time to make i2o_block the driver of choice for this line of
controllers. I then reacted to the rejection by working with Markus
Lidel to move the 64 bit capabilities into the i2o driver.
Sincerely -- Mark Salyzyn
next prev parent reply other threads:[~2007-12-11 16:07 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 ` Salyzyn, Mark [this message]
2007-12-11 21:53 ` Miquel van Smoorenburg
2007-12-12 13:25 ` broken dpt_i2o in 2.6.23 (was: ext2_check_page: bad entry indirectory) (fwd) Salyzyn, Mark
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=AE4F746F2AECFC4DA4AADD66A1DFEF0101052133@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
all inboxes | Powered by JetHome®