From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 16010] New: Mptlinux update problem but need
Date: Thu, 20 May 2010 07:24:10 GMT [thread overview]
Message-ID: <bug-16010-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16010
Summary: Mptlinux update problem but need
Product: SCSI Drivers
Version: 2.5
Kernel Version: 2.6.32
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
ReportedBy: fantonifabio@tiscali.it
Regression: No
For Omsa 6.0.1 is need mptlinux version more than 3.04 present in kernel
I have download 4.22 from lsi site and try build update driver with dkms, i
have already do same on 2.6.26 past without problem but with 2.6.32 give this
compilation error:
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c: In function
‘mptsas_smp_handler’:
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2757: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2758: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2775: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2805: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2808: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2821: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2823: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2854: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2855: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2864: error: ‘struct request’
has no member named ‘data_len’
/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2867: error: ‘struct request’
has no member named ‘data_len’
make[3]: *** [/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.o] Error 1
make[2]: *** [_module_/var/lib/dkms/mptlinux/4.22.00.00/build] Error 2
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2
Is possible update mptlinux on new kernel version please?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-05-20 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 7:24 bugzilla-daemon [this message]
2010-05-21 9:33 ` [Bug 16010] Mptlinux update problem but need bugzilla-daemon
2010-05-21 14:04 ` [Bug 16010] New: " James Bottomley
2010-05-21 14:05 ` [Bug 16010] " bugzilla-daemon
2010-07-12 15:30 ` bugzilla-daemon
2012-07-12 13:27 ` bugzilla-daemon
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=bug-16010-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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;
as well as URLs for NNTP newsgroup(s).