From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jes Sorensen <jes@trained-monkey.org>,
Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-scsi@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] sym53c8xx_2: fix compilation on alpha
Date: Sun, 15 Jan 2006 18:27:20 -0600 [thread overview]
Message-ID: <1137371240.3511.17.camel@mulgrave> (raw)
In-Reply-To: <20060116000035.GA3794@mipter.zuzino.mipt.ru>
On Mon, 2006-01-16 at 03:00 +0300, Alexey Dobriyan wrote:
> CC [M] drivers/scsi/sym53c8xx_2/sym_fw.o
> In file included from drivers/scsi/sym53c8xx_2/sym_glue.h:59,
> from drivers/scsi/sym53c8xx_2/sym_fw.c:40:
> include/scsi/scsi_transport_spi.h:57: error: field `dv_mutex' has incomplete type
> --- a/drivers/scsi/sym53c8xx_2/sym_hipd.c
> +++ b/drivers/scsi/sym53c8xx_2/sym_hipd.c
> @@ -39,6 +39,7 @@
> */
>
> #include <linux/slab.h>
> +#include <linux/mutex.h>
Actually, this isn't the right fix. The problem lies in the conversion
of the transport class from semaphore to mutex, so the include belongs
in scsi_transport_spi.h
In theory, it could be a simple 'struct mutex' declaration, since no
driver ever uses it, but I'm afraid gcc might not be happy dereferencing
members of a structure containing a type of unknown size (even if it is
at the end).
James
diff --git a/include/scsi/scsi_transport_spi.h b/include/scsi/scsi_transport_spi.h
--- a/include/scsi/scsi_transport_spi.h
+++ b/include/scsi/scsi_transport_spi.h
@@ -21,6 +21,7 @@
#define SCSI_TRANSPORT_SPI_H
#include <linux/config.h>
+#include <linux/mutex.h>
#include <linux/transport_class.h>
struct scsi_transport_template;
prev parent reply other threads:[~2006-01-16 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 0:00 [PATCH] sym53c8xx_2: fix compilation on alpha Alexey Dobriyan
2006-01-16 0:27 ` James Bottomley [this message]
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=1137371240.3511.17.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=adobriyan@gmail.com \
--cc=jes@trained-monkey.org \
--cc=linux-scsi@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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