From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Tarjei Huse <tarjei@nu.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: Fri, 12 Jan 2007 15:37:35 -0800 [thread overview]
Message-ID: <45A81BBF.7050104@us.ibm.com> (raw)
In-Reply-To: <45A6C33C.8060900@scanventure.no>
Tarjei Huse wrote:
> I did the opposite, I downloaded the git tree and tried to compile it.
> Since I got an error, I added the scsi-rc-fixes patch (the scsi-misc and
> aic94xx didn't apply cleanly so I guessed they were already in the git
> tree), the 39-libsas-fix-thypos,
> ../11-aic94xx-dont-eat-query-task-results_1, 17-aic94xx-fix-fw-leak_1.
The aic94xx-sas git tree is a requirement. Something along the lines of:
$ cg-clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ cd linux-2.6
$ cg-branch-add scsi-misc git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
$ cg-branch-add scsi-rc git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
$ cg-branch-add aic94xx git://git.kernel.org/pub/scm/linux/kernel/git/jejb/aic94xx-sas-2.6.git
$ cg-update scsi-misc
$ cg-update scsi-rc
$ cg-update aic94xx
*Then* apply patches from my patch set.
--D
next prev parent reply other threads:[~2007-01-12 23:37 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
[not found] ` <45A6C33C.8060900@scanventure.no>
2007-01-12 23:37 ` Darrick J. Wong [this message]
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=45A81BBF.7050104@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@nu.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.