From: Samuel Ortiz <sameo@linux.intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Cyril Chemparathy <cyril@ti.com>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: ti-ssp: Fix build
Date: Mon, 18 Nov 2013 10:29:13 +0100 [thread overview]
Message-ID: <20131118092913.GD17681@zurbaran> (raw)
In-Reply-To: <1384714435-30474-1-git-send-email-geert@linux-m68k.org>
Hi Geert,
On Sun, Nov 17, 2013 at 07:53:55PM +0100, Geert Uytterhoeven wrote:
> drivers/mfd/ti-ssp.c: In function 'ti_ssp_run':
> drivers/mfd/ti-ssp.c:286:2: error: implicit declaration of function 'set_current_state' [-Werror=implicit-function-declaration]
> drivers/mfd/ti-ssp.c:286:381: error: 'TASK_INTERRUPTIBLE' undeclared (first use in this function)
> drivers/mfd/ti-ssp.c:286:381: note: each undeclared identifier is reported only once for each function it appears in
> drivers/mfd/ti-ssp.c:286:2: error: implicit declaration of function 'signal_pending' [-Werror=implicit-function-declaration]
> drivers/mfd/ti-ssp.c:286:2: error: implicit declaration of function 'schedule' [-Werror=implicit-function-declaration]
> drivers/mfd/ti-ssp.c:286:2: error: implicit declaration of function '__set_current_state' [-Werror=implicit-function-declaration]
> drivers/mfd/ti-ssp.c:286:742: error: 'TASK_RUNNING' undeclared (first use in this function)
> drivers/mfd/ti-ssp.c: In function 'ti_ssp_interrupt':
> drivers/mfd/ti-ssp.c:311:32: error: 'TASK_NORMAL' undeclared (first use in this function)
>
> Add missing #include <linux/sched.h>.
>
> drivers/mfd/ti-ssp.c: In function 'ti_ssp_probe':
> drivers/mfd/ti-ssp.c:412:12: error: 'struct mfd_cell' has no member named 'data_size'
>
Applied to mfd-fixes, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2013-11-18 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 18:53 [PATCH] mfd: ti-ssp: Fix build Geert Uytterhoeven
2013-11-18 9:29 ` Samuel Ortiz [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=20131118092913.GD17681@zurbaran \
--to=sameo@linux.intel.com \
--cc=cyril@ti.com \
--cc=geert@linux-m68k.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@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