All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-c6x-dev@linux-c6x.org,
	Aurelien Jacquiot <jacquiot.aurelien@gmail.com>,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH] c6x: fix platforms/plldata.c get_coreid build error
Date: Tue, 23 Jan 2018 18:15:21 -0500	[thread overview]
Message-ID: <1516749321.2957.44.camel@redhat.com> (raw)
In-Reply-To: <2fe9d4b5-ad6b-8d64-9dc5-4440e23948fc@infradead.org>

On Fri, 2018-01-19 at 11:19 -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Fix build error reported by the 0day bot by including the header
> file for that macro.

Thanks. I pulled this into the c6x tree.

> 
> 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>
>  
>  /*
> 

      reply	other threads:[~2018-01-23 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 19:19 [PATCH] c6x: fix platforms/plldata.c get_coreid build error Randy Dunlap
2018-01-23 23:15 ` Mark Salter [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=1516749321.2957.44.camel@redhat.com \
    --to=msalter@redhat.com \
    --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=rdunlap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.