From: Mason <slash.tmp@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] package/linux-fusion: 'struct msghdr' has no member named 'msg_iov'
Date: Wed, 6 Jan 2016 14:09:16 +0100 [thread overview]
Message-ID: <568D11FC.5030103@free.fr> (raw)
In-Reply-To: <568BBD3F.2030607@free.fr>
On 05/01/2016 13:55, Mason wrote:
> The linux-fusion package fails to build with recent kernels.
Might as well fix the other issue, while I'm at it.
Would my two fusion patches be accepted in buildroot if I make a
formal submission? (Who would review them?)
Looks like the upstream project is hibernating.
Regards.
linux-fusion-9.0.3/linux/drivers/char/fusion/fusiondev.c: In function 'call_ioctl':
linux-fusion-9.0.3/linux/drivers/char/fusion/fusiondev.c:775:39: warning: format '%ld' expects argument of type 'long int', but argument 7 has type 'int' [-Wformat=]
diff --git a/linux/drivers/char/fusion/fusiondev.c b/linux/drivers/char/fusion/fusiondev.c
index 7003407f7e1e..b145d7effa89 100644
--- a/linux/drivers/char/fusion/fusiondev.c
+++ b/linux/drivers/char/fusion/fusiondev.c
@@ -772,10 +772,11 @@ call_ioctl(FusionDev * dev, Fusionee * fusionee,
if (!(execute3.flags & FCEF_DONE)) {
if (execute3.flags & FCEF_ERROR) {
+ long diff = execute3_bin - (FusionCallExecute3 *)arg;
printk( KERN_ERR "fusion: FUSION_CALL_EXECUTE3 with errorneous call (failed on previous ioctl call), "
"call id %d, flags 0x%08x, arg %d, length %u, serial %u, %ld\n",
execute3.call_id, execute3.flags, execute3.call_arg, execute3.length, execute3.ret_length,
- (execute3_bin - (FusionCallExecute3 *) arg) );
+ diff);
return -EIO;
}
next prev parent reply other threads:[~2016-01-06 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 12:55 [Buildroot] package/linux-fusion: 'struct msghdr' has no member named 'msg_iov' Mason
2016-01-05 14:33 ` Mason
2016-01-06 13:09 ` Mason [this message]
2016-01-06 16:35 ` Mason
2016-01-12 15:10 ` Mason
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=568D11FC.5030103@free.fr \
--to=slash.tmp@free.fr \
--cc=buildroot@busybox.net \
/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