From: Randy Dunlap <rdunlap@infradead.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-c6x-dev@linux-c6x.org,
Aurelien Jacquiot <jacquiot.aurelien@gmail.com>,
Mark Salter <msalter@redhat.com>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: [PATCH] c6x: fix platforms/plldata.c get_coreid build error
Date: Fri, 19 Jan 2018 11:19:33 -0800 [thread overview]
Message-ID: <2fe9d4b5-ad6b-8d64-9dc5-4440e23948fc@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Fix build error reported by the 0day bot by including the header
file for that macro.
Fixes this build error: (should fix; not tested)
arch/c6x/platforms/plldata.c: In function 'c6472_setup_clocks':
arch/c6x/platforms/plldata.c:279:33: error: implicit declaration of function 'get_coreid'; did you mean 'get_order'? [-Werror=implicit-function-declaration]
c6x_core_clk.parent = &sysclks[get_coreid() + 1];
Reported-by: Fengguang Wu <fengguang.wu@intel.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Aurelien Jacquiot <jacquiot.aurelien@gmail.com>
Cc: linux-c6x-dev@linux-c6x.org
Cc: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
arch/c6x/platforms/plldata.c | 1 +
1 file changed, 1 insertion(+)
--- lnx-415-rc8.orig/arch/c6x/platforms/plldata.c
+++ lnx-415-rc8/arch/c6x/platforms/plldata.c
@@ -19,6 +19,7 @@
#include <asm/clock.h>
#include <asm/setup.h>
+#include <asm/special_insns.h>
#include <asm/irq.h>
/*
next reply other threads:[~2018-01-19 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 19:19 Randy Dunlap [this message]
2018-01-23 23:15 ` [PATCH] c6x: fix platforms/plldata.c get_coreid build error Mark Salter
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=2fe9d4b5-ad6b-8d64-9dc5-4440e23948fc@infradead.org \
--to=rdunlap@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=jacquiot.aurelien@gmail.com \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=msalter@redhat.com \
/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).