Re: [PATCH] [BUG] clk: rockchip: don't mark clock names as initconst

2016-01-02 Thread Michael Turquette
Quoting Heiko Stübner (2016-01-01 14:05:10) > Am Freitag, 1. Januar 2016, 22:50:43 schrieb Arnd Bergmann: > > On Friday 01 January 2016 18:06:30 Heiko Stübner wrote: > > > "[PATCH] clk: rockchip: fix section mismatches with new child-clocks" [0] > > > > > > should be in Mike's + Stephen's inbox si

Re: [PATCH] [BUG] clk: rockchip: don't mark clock names as initconst

2016-01-01 Thread Heiko Stübner
Am Freitag, 1. Januar 2016, 22:50:43 schrieb Arnd Bergmann: > On Friday 01 January 2016 18:06:30 Heiko Stübner wrote: > > "[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 n

Re: [PATCH] [BUG] clk: rockchip: don't mark clock names as initconst

2016-01-01 Thread Arnd Bergmann
On Friday 01 January 2016 18:06:30 Heiko Stübner wrote: > > "[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

Re: [PATCH] [BUG] clk: rockchip: don't mark clock names as initconst

2016-01-01 Thread Heiko Stübner
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 __compoun

[PATCH] [BUG] clk: rockchip: don't mark clock names as initconst

2016-01-01 Thread 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