From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Tarjei Huse <tarjei@scanventure.no>
Cc: dougg@torque.net, linux-scsi@vger.kernel.org, "Wu,
Gilbert" <Gilbert_Wu@adaptec.com>,
"Chim, Ed" <ed_chim@adaptec.com>,
Alexis Bruemmer <alexisb@us.ibm.com>
Subject: Re: Adaptect 9405w: What is the best solution?
Date: Thu, 11 Jan 2007 12:08:23 -0800 [thread overview]
Message-ID: <45A69937.8030400@us.ibm.com> (raw)
In-Reply-To: <45A694A1.6010400@scanventure.no>
Tarjei Huse wrote:
> Ok, I haven't tested a git tree yet, but what you're saying is that I
> should download just this git tree and use it, right?
I suppose you could do that with some patch massaging, though at the
moment the patches are based off 2.6.20-rc4 + scsi-misc + scsi-rc-fixes
+ aic94xx-sas and will probably generate quite a bit of fuzz when
applied against anything else.
> http://www.kernel.org/git/?p=linux/kernel/git/jejb/aic94xx-sas-2.6.git;a=summary
> Or should I just download the the patches you mention and
...and? I think your message got truncated?
> What patches? Are they related to the aic driver or are they related to
> other things you are testing? (i.e. do I run a risk by using them?
All of those patches fix problems seen while testing/beating/exercising
the aic94xx driver.
> Also, when will this work land in the mainline kernel tree?
Hopefully sooner than later.
--D
next prev parent reply other threads:[~2007-01-11 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 11:02 Adaptect 9405w: What is the best solution? Tarjei Huse
2007-01-11 15:26 ` Douglas Gilbert
2007-01-11 19:30 ` Darrick J. Wong
2007-01-11 19:48 ` Tarjei Huse
2007-01-11 20:08 ` Darrick J. Wong [this message]
[not found] ` <45A6C33C.8060900@scanventure.no>
2007-01-12 23:37 ` Darrick J. Wong
2007-01-14 15:30 ` Tarjei Huse
[not found] ` <45AA4A7B.7070607@scanventure.no>
2007-01-15 20:50 ` Darrick J. Wong
2007-01-16 14:12 ` Tarjei Huse
2007-01-16 23:14 ` Alexis Bruemmer
2007-01-17 10:51 ` Tarjei Huse
2007-01-17 16:32 ` Mark Rustad
2007-01-17 16:54 ` James Bottomley
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=45A69937.8030400@us.ibm.com \
--to=djwong@us.ibm.com \
--cc=Gilbert_Wu@adaptec.com \
--cc=alexisb@us.ibm.com \
--cc=dougg@torque.net \
--cc=ed_chim@adaptec.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tarjei@scanventure.no \
/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.