From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] aic94xx: move entirely over to correct transport class formulation
Date: Mon, 27 Mar 2006 21:39:02 -0800 [thread overview]
Message-ID: <20060328053902.GA15968@us.ibm.com> (raw)
In-Reply-To: <1143499534.3334.33.camel@mulgrave.il.steeleye.com>
James Bottomley <James.Bottomley@SteelEye.com> wrote:
> +#include <scsi/scsi_transport.h>
> +#include <scsi/scsi_transport_sas.h>
> +#include "../scsi_sas_internal.h"
I did a git pull from the aic tree and scsi-misc, and applied your patch.
Was scsi_sas_internal.h suppose to be in this patch?
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2006-03-28 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 22:45 [PATCH] aic94xx: move entirely over to correct transport class formulation James Bottomley
2006-03-28 5:39 ` Mike Anderson [this message]
2006-03-28 15:06 ` James Bottomley
2006-03-28 15:28 ` James Bottomley
2006-03-28 15:07 ` Christoph Hellwig
2006-03-28 15:13 ` 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=20060328053902.GA15968@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@SteelEye.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox