From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
"Tarte, Robert" <Robert_Tarte@adaptec.com>
Subject: Re: aic94xx tree up on www.kernel.org
Date: Mon, 6 Mar 2006 14:44:58 -0800 [thread overview]
Message-ID: <20060306224458.GA7797@us.ibm.com> (raw)
In-Reply-To: <1141669543.3167.25.camel@mulgrave.il.steeleye.com>
James Bottomley <James.Bottomley@SteelEye.com> wrote:
> I've put it at
>
> http://www.kernel.org/git/?p=linux/kernel/git/jejb/aic94xx-sas-2.6.git;a=summary
>
> With the rolled up patches and change logs at:
>
> http://www.kernel.org/pub/linux/kernel/people/jejb/
I am hitting an error trying to compile the tree due to the define for
struct sas_end_device missing. I saw usage added in "Further updates:". I
guess I can reverse these changes to get it to compile or do you have the
define and it just did not get added?
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2006-03-06 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 18:25 aic94xx tree up on www.kernel.org James Bottomley
2006-03-06 22:44 ` Mike Anderson [this message]
2006-03-06 23:23 ` 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=20060306224458.GA7797@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Robert_Tarte@adaptec.com \
--cc=linux-scsi@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 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.