From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [BUG] clk: rockchip: don't mark clock names as initconst
Date: Fri, 01 Jan 2016 18:06:30 +0100 [thread overview]
Message-ID: <1799610.nrn5HMCSxL@diego> (raw)
In-Reply-To: <2791943.MBZ53mI7Gp@wuerfel>
Hi Arnd,
Am Freitag, 1. Januar 2016, 14:42:52 schrieb Arnd Bergmann:
> The latest changes to the rockchip clk implementation cause
> tons of warnings and/or errors (depending on the configuration):
>
> WARNING: vmlinux.o(.data+0x125394): Section mismatch in reference from the
> variable __compound_literal.125 to the (unknown reference)
> .init.rodata:(unknown)
>
> The reason is a compount literal in a macro that refers to an
> object in the .init.rodata section:
>
> #define COMPOSITE_FRACMUX(_id, cname, pname, f, mo, df, go, gs, gf, ch) \
> { \
> ...
> .child = &(struct rockchip_clk_branch)ch, \
> }
>
> 'ch' here is placed in .data, and I could find no way to override that
> using an attribute or pragma because there is no identifier associated
> with it.
"[PATCH] clk: rockchip: fix section mismatches with new child-clocks" [0]
should be in Mike's + Stephen's inbox since last week as well, which moves the
offending new elements into separate entities, which can have __initdata
attributes again.
Heiko
[0] http://www.spinics.net/lists/arm-kernel/msg471295.html
next prev parent reply other threads:[~2016-01-01 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 13:42 [PATCH] [BUG] clk: rockchip: don't mark clock names as initconst Arnd Bergmann
2016-01-01 17:06 ` Heiko Stübner [this message]
2016-01-01 21:50 ` Arnd Bergmann
2016-01-01 22:05 ` Heiko Stübner
2016-01-02 21:42 ` Michael Turquette
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=1799610.nrn5HMCSxL@diego \
--to=heiko@sntech.de \
--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;
as well as URLs for NNTP newsgroup(s).