From: Tom Duffy <tduffy@sun.com>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Olaf Hering <olh@suse.de>
Subject: RE: [PATCH 22/82] remove linux/version.h from drivers/message/fus ion
Date: Tue, 12 Jul 2005 13:56:33 -0700 [thread overview]
Message-ID: <1121201793.14638.10.camel@duffman> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C03157047@nacos172.co.lsil.com>
[-- Attachment #1: Type: text/plain, Size: 3336 bytes --]
On Tue, 2005-07-12 at 14:50 -0600, Moore, Eric Dean wrote:
> The 3.02.18 driver and the driver in kernel tree are totally different
> drivers.
> One thing is 3.02.18 has SAS support, and the kernel tree doesn't. Id
> wish
> kernel folks would take our SAS drivers.
Is there a patch that applies cleanly to 2.6.13-rc2? I would like that
as a starting point, at least.
I noticed that the 3.02.18 drivers have a bunch of compile warnings on
the latest kernel. It won't even link against mm.
make -C /build1/tduffy/openib-work/build/mm/x86_64/ M=/build1/tduffy/openib-work/mptlinux-3.02.18/fusion modules
make[1]: Entering directory `/build1/tduffy/openib-work/build/mm/x86_64'
make -C /build1/tduffy/openib-work/linux-2.6.13-rc-mm O=/build1/tduffy/openib-work/build/mm/x86_64 modules
CC [M] /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptbase.o
CC [M] /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptscsih.o
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptscsih.c: In function ‘mptscsih_probe’:
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptscsih.c:1195: warning: implicit declaration of function ‘scsi_set_device’
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptscsih.c: At top level:
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptscsih.c:3815: warning: initialization from incompatible pointer type
CC [M] /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptlan.o
CC [M] /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.o
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.c: In function ‘mptctl_init’:
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.c:3735: warning: implicit declaration of function ‘register_ioctl32_conversion’
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.c:3856: warning: implicit declaration of function ‘unregister_ioctl32_conversion’
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.c: In function ‘mptctl_do_mpt_command’:
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.c:2007: warning: ‘bufIn.len’ may be used uninitialized in this function
/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.c:2008: warning: ‘bufOut.len’ may be used uninitialized in this function
Building modules, stage 2.
MODPOST
*** Warning: "scsi_set_device" [/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptscsih.ko] undefined!
*** Warning: "unregister_ioctl32_conversion" [/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.ko] undefined!
*** Warning: "register_ioctl32_conversion" [/build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.ko] undefined!
CC /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptbase.mod.o
LD [M] /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptbase.ko
CC /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.mod.o
LD [M] /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptctl.ko
CC /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptlan.mod.o
LD [M] /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptlan.ko
CC /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptscsih.mod.o
LD [M] /build1/tduffy/openib-work/mptlinux-3.02.18/fusion/mptscsih.ko
make[1]: Leaving directory `/build1/tduffy/openib-work/build/mm/x86_64'
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-12 20:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 20:50 [PATCH 22/82] remove linux/version.h from drivers/message/fus ion Moore, Eric Dean
2005-07-12 20:56 ` Tom Duffy [this message]
2005-07-12 22:14 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2005-07-20 0:07 Moore, Eric Dean
2005-07-20 3:12 ` Matt Domsch
2005-07-20 4:28 ` Stephen Rothwell
2005-07-20 5:09 ` Moore, Eric Moore
2005-07-20 5:09 ` Moore, Eric Moore
2005-07-20 8:30 ` Bernd Petrovitsch
2005-07-20 12:48 ` Matthew Wilcox
2005-07-20 17:54 ` Nathan Lynch
2005-07-20 18:22 ` Matt Domsch
2005-07-20 17:55 ` Nish Aravamudan
2005-07-13 15:11 Moore, Eric Dean
2005-07-12 22:34 Moore, Eric Dean
2005-07-11 0:15 Moore, Eric Dean
2005-07-12 20:30 ` Tom Duffy
2005-07-13 2:16 ` Matt Domsch
2005-07-13 14:37 ` Christoph Hellwig
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=1121201793.14638.10.camel@duffman \
--to=tduffy@sun.com \
--cc=Eric.Moore@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=olh@suse.de \
/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.