From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Magnus Damm <damm+renesas@opensource.se>,
Simon Horman <horms+renesas@verge.net.au>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: fix link error for rcar-gen2
Date: Fri, 21 Oct 2016 19:42:42 +0300 [thread overview]
Message-ID: <9f16dc0d-fe5e-dff8-e461-9e0dfdd23da7@cogentembedded.com> (raw)
In-Reply-To: <20161021154737.3803065-1-arnd@arndb.de>
Hello.
On 10/21/2016 06:47 PM, Arnd Bergmann wrote:
> The addition of one more rcar-gen2 based SoC caused a build error (again)
> in my randconfig builds:
>
> arch/arm/mach-shmobile/setup-rcar-gen2.o: In function `rcar_gen2_timer_init':
> setup-rcar-gen2.c:(.init.text+0x200): undefined reference to `rcar_gen2_clocks_init'
OK, seeing how you got this -- I should have tested the kernel build with
only R8A7743 enabled... sorry about that. :-<
I probably shouldn't have used rcar_gen2_timer_init() in the 1st place...
> I think this has happened twice in the past. Instead of adding each SoC
> one at a time, this changes the existing list to always build the
> rcar-gen2 related clk files whenever the generic symbol is selected.
The problem is we're not going to use this driver on RZ/G SoCs... The
newer rcar2-cpg-mssr.c will be used instead -- I submitted the patches for
that before ELC-E...
> Fixes: 1254f607fc3d ("ARM: shmobile: r8a7743: basic SoC support")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
[...]
MBR, Sergei
next prev parent reply other threads:[~2016-10-21 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 15:47 [PATCH] clk: fix link error for rcar-gen2 Arnd Bergmann
2016-10-21 16:42 ` Sergei Shtylyov [this message]
2016-10-21 18:01 ` Geert Uytterhoeven
2016-10-21 21:07 ` Arnd Bergmann
2016-10-25 8:37 ` Geert Uytterhoeven
2016-10-31 9:23 ` Geert Uytterhoeven
2016-10-31 9:52 ` Simon Horman
2016-10-31 10:02 ` Geert Uytterhoeven
2016-11-01 9:28 ` Simon Horman
2016-11-02 8:14 ` Geert Uytterhoeven
2016-11-02 8:37 ` Simon Horman
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=9f16dc0d-fe5e-dff8-e461-9e0dfdd23da7@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=arnd@arndb.de \
--cc=damm+renesas@opensource.se \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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