From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matt Domsch <Matt_Domsch@Dell.com>, atulm@lsil.com
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: merge megaraid 2.20.x in kernel 2.6?
Date: 17 Aug 2004 12:40:33 -0400 [thread overview]
Message-ID: <1092760835.1775.303.camel@mulgrave> (raw)
In-Reply-To: <20040817160128.GA7127@lists.us.dell.com>
On Tue, 2004-08-17 at 12:01, Matt Domsch wrote:
> James, is there anything you're still waiting on before merging the
> LSI megaraid 2.20.x driver into your scsi-misc-2.6 tree? I thought
> the agreement by you, Christoph, and Atul was to get it merged, and
> then fix up the few outstanding concerns post-merge.
OK, I forgot in the rush of conferences.
I did put it in, but it fails to compile on parisc:
In file included from drivers/scsi/megaraid/megaraid_mm.c:18:
drivers/scsi/megaraid/megaraid_mm.h:51:25: asm/ioctl32.h: No such file
or directory
drivers/scsi/megaraid/megaraid_mm.c: In function `mraid_mm_init':
drivers/scsi/megaraid/megaraid_mm.c:1069: warning: implicit declaration
of function `register_ioctl32_conversion'
drivers/scsi/megaraid/megaraid_mm.c: In function `mraid_mm_exit':
drivers/scsi/megaraid/megaraid_mm.c:1098: warning: implicit declaration
of function `unregister_ioctl32_conversion'
make[3]: *** [drivers/scsi/megaraid/megaraid_mm.o] Error 1
make[2]: *** [drivers/scsi/megaraid] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2
It looks like the compat ioctl infrastructure is incorrect.
James
next prev parent reply other threads:[~2004-08-17 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 16:01 merge megaraid 2.20.x in kernel 2.6? Matt Domsch
2004-08-17 16:40 ` James Bottomley [this message]
2004-08-17 16:47 ` Christoph Hellwig
2004-08-17 16:51 ` Matt Domsch
2004-08-17 16:58 ` James Bottomley
2004-08-17 17:06 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 17:58 Mukker, Atul
2004-08-26 22:03 Mukker, Atul
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=1092760835.1775.303.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Matt_Domsch@Dell.com \
--cc=atulm@lsil.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