From: rick.chang@mediatek.com (Rick Chang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] [media] vcodec: mediatek: add missing linux/slab.h include
Date: Tue, 21 Mar 2017 09:22:15 +0800 [thread overview]
Message-ID: <1490059335.27725.7.camel@mtksdaap41> (raw)
In-Reply-To: <20170320094812.1365229-1-arnd@arndb.de>
Hi Arnd,
Thank you for the patch, but someone has fixed the same problem.
Regards,
Rick
On Mon, 2017-03-20 at 10:47 +0100, Arnd Bergmann wrote:
> With the newly added driver, I have run into randconfig failures like:
>
> drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c: In function 'mtk_jpeg_open':
> drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c:1017:8: error: implicit declaration of function 'kzalloc';did you mean 'kvzalloc'? [-Werror=implicit-function-declaration]
>
> Including the header with the declaration solves the problem.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c b/drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c
> index b10183f7942b..f9bd58ce7d32 100644
> --- a/drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c
> +++ b/drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c
> @@ -22,6 +22,7 @@
> #include <linux/of_platform.h>
> #include <linux/platform_device.h>
> #include <linux/pm_runtime.h>
> +#include <linux/slab.h>
> #include <linux/spinlock.h>
> #include <media/v4l2-event.h>
> #include <media/v4l2-mem2mem.h>
prev parent reply other threads:[~2017-03-21 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 9:47 [PATCH 1/2] [media] vcodec: mediatek: add missing linux/slab.h include Arnd Bergmann
2017-03-20 9:47 ` [PATCH 2/2] [media] vcodec: mediatek: mark pm functions as __maybe_unused Arnd Bergmann
2017-03-21 1:46 ` Rick Chang
2017-03-21 1:22 ` Rick Chang [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=1490059335.27725.7.camel@mtksdaap41 \
--to=rick.chang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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