public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: "Moore, Eric Dean" <Eric.Moore@lsil.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: RE: As of 2.6.13-rc1 Fusion-MPT very slow
Date: Sat, 06 Aug 2005 17:07:43 -0500	[thread overview]
Message-ID: <1123366064.5102.3.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.61.0508062058200.27998@praktifix.dwd.de>

On Sat, 2005-08-06 at 21:12 +0000, Holger Kiehl wrote:
> I tried from 2.6.13-rc2-mm2 up to 2.6.13-rc4-mm1 and always get the following
> error when applying this patch:
> 
>       CC      drivers/message/fusion/mptbase.o
>       CC      drivers/message/fusion/mptscsih.o
>       CC      drivers/message/fusion/mptspi.o
>     drivers/message/fusion/mptspi.c: In function â..mptspi_target_allocâ..:
>     drivers/message/fusion/mptspi.c:113: error: invalid storage class for function â..mptspi_write_offsetâ..
>     drivers/message/fusion/mptspi.c:114: error: invalid storage class for function â..mptspi_write_widthâ..
>     drivers/message/fusion/mptspi.c:131: warning: implicit declaration of function â..mptspi_write_widthâ..
>     drivers/message/fusion/mptspi.c: At top level:
>     drivers/message/fusion/mptspi.c:453: warning: conflicting types for â..mptspi_write_widthâ..
>     drivers/message/fusion/mptspi.c:453: error: static declaration of â..mptspi_write_widthâ.. follows non-static declaration
>     drivers/message/fusion/mptspi.c:131: error: previous implicit declaration of â..mptspi_write_widthâ.. was here

This lot are all gcc-4 being silly about a declaration, as you noticed.
Still, there's no reason not to make the static functions declared at
the top of the file.

>     drivers/message/fusion/mptspi.c:505: error: unknown field â..get_hold_mcsâ.. specified in initializer
>     drivers/message/fusion/mptspi.c:505: warning: excess elements in struct initializer
>     drivers/message/fusion/mptspi.c:505: warning: (near initialization for â..mptspi_transport_functionsâ..)
>     drivers/message/fusion/mptspi.c:506: error: unknown field â..set_hold_mcsâ.. specified in initializer
>     drivers/message/fusion/mptspi.c:506: warning: excess elements in struct initializer
>     drivers/message/fusion/mptspi.c:506: warning: (near initialization for â..mptspi_transport_functionsâ..)
>     drivers/message/fusion/mptspi.c:507: error: unknown field â..show_hold_mcsâ.. specified in initializer
>     drivers/message/fusion/mptspi.c:507: warning: excess elements in struct initializer
>     drivers/message/fusion/mptspi.c:507: warning: (near initialization for â..mptspi_transport_functionsâ..)

This is actually because -mm is slightly behind the scsi-misc tree.  It
looks like the hold_mcs parameters haven't propagated into the -mm tree
yet.  You should be able to correct this by cutting these three lines:

	.get_hold_mcs	= mptspi_read_parameters,
	.set_hold_mcs	= mptspi_write_hold_mcs,
	.show_hold_mcs	= 1,

Out of the code at lines 505-507.  You'll get a warning about
mptspi_write_hold_mcs() being defined but not used which you can ignore.

James



  reply	other threads:[~2005-08-06 22:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01 15:31 As of 2.6.13-rc1 Fusion-MPT very slow Moore, Eric Dean
2005-08-01 15:40 ` Holger Kiehl
2005-08-06 17:53   ` James Bottomley
2005-08-06 21:12     ` Holger Kiehl
2005-08-06 22:07       ` James Bottomley [this message]
2005-08-07  5:59         ` Holger Kiehl
2005-08-07 14:29           ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2005-08-08 18:27 Moore, Eric Dean
2005-08-09 12:16 ` Holger Kiehl
2005-08-30 15:28   ` tony.luck
2005-08-30 21:49     ` tony.luck
     [not found] <91888D455306F94EBD4D168954A9457C035CB329@nacos172.co.lsil.com>
2005-07-30  0:51 ` Andrew Morton
2005-08-01 10:15   ` Holger Kiehl
2005-07-26 10:52 Holger Kiehl

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=1123366064.5102.3.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=Eric.Moore@lsil.com \
    --cc=Holger.Kiehl@dwd.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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