From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Subject: Re: linux-next: Tree for Feb 19 (rapidio: rio_mport_cdev.c)
Date: Fri, 19 Feb 2016 11:07:00 -0800 [thread overview]
Message-ID: <56C767D4.1010003@infradead.org> (raw)
In-Reply-To: <20160219154952.1bb036cd@canb.auug.org.au>
On 02/18/16 20:49, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160218:
>
on x86_64 (for the past 3 days or so):
when CONFIG_DMA_ENGINE is not enabled:
../drivers/rapidio/devices/rio_mport_cdev.c: In function 'mport_cdev_open':
../drivers/rapidio/devices/rio_mport_cdev.c:1938:22: error: 'struct mport_cdev_priv' has no member named 'async_list'
INIT_LIST_HEAD(&priv->async_list);
^
../drivers/rapidio/devices/rio_mport_cdev.c:1939:22: error: 'struct mport_cdev_priv' has no member named 'pend_list'
INIT_LIST_HEAD(&priv->pend_list);
^
In file included from ../include/linux/seqlock.h:35:0,
from ../include/linux/time.h:5,
from ../include/linux/stat.h:18,
from ../include/linux/module.h:10,
from ../drivers/rapidio/devices/rio_mport_cdev.c:17:
../drivers/rapidio/devices/rio_mport_cdev.c:1941:22: error: 'struct mport_cdev_priv' has no member named 'req_lock'
spin_lock_init(&priv->req_lock);
^
../include/linux/spinlock.h:296:17: note: in definition of macro 'spin_lock_init'
spinlock_check(_lock); \
^
In file included from ../include/linux/seqlock.h:35:0,
from ../include/linux/time.h:5,
from ../include/linux/stat.h:18,
from ../include/linux/module.h:10,
from ../drivers/rapidio/devices/rio_mport_cdev.c:17:
../drivers/rapidio/devices/rio_mport_cdev.c:1941:22: error: 'struct mport_cdev_priv' has no member named 'req_lock'
spin_lock_init(&priv->req_lock);
^
../include/linux/spinlock.h:99:24: note: in definition of macro 'raw_spin_lock_init'
__raw_spin_lock_init((lock), #lock, &__key); \
^
../drivers/rapidio/devices/rio_mport_cdev.c:1941:2: note: in expansion of macro 'spin_lock_init'
spin_lock_init(&priv->req_lock);
^
../drivers/rapidio/devices/rio_mport_cdev.c: In function 'mport_cdev_ioctl':
../drivers/rapidio/devices/rio_mport_cdev.c:2172:3: error: implicit declaration of function 'rio_mport_alloc_dma' [-Werror=implicit-function-declaration]
return rio_mport_alloc_dma(filp, (void __user *)arg);
^
../drivers/rapidio/devices/rio_mport_cdev.c:2174:3: error: implicit declaration of function 'rio_mport_free_dma' [-Werror=implicit-function-declaration]
return rio_mport_free_dma(filp, (void __user *)arg);
^
../drivers/rapidio/devices/rio_mport_cdev.c:2176:3: warning: passing argument 2 of 'rio_mport_wait_for_async_dma' makes integer from pointer without a cast [enabled by default]
return rio_mport_wait_for_async_dma(filp, (void __user *)arg);
^
../drivers/rapidio/devices/rio_mport_cdev.c:1136:12: note: expected 'int32_t' but argument is of type 'void *'
static int rio_mport_wait_for_async_dma(struct file *filp, int32_t arg)
^
--
~Randy
prev parent reply other threads:[~2016-02-19 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 4:49 linux-next: Tree for Feb 19 Stephen Rothwell
2016-02-19 19:07 ` Randy Dunlap [this message]
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=56C767D4.1010003@infradead.org \
--to=rdunlap@infradead.org \
--cc=alexandre.bounine@idt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mporter@kernel.crashing.org \
--cc=sfr@canb.auug.org.au \
/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).