[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3926467.jaQRQH5bEO@diego>
Date: Fri, 01 Jan 2016 23:05:10 +0100
From: Heiko Stübner <heiko@...ech.de>
To: Arnd Bergmann <arnd@...db.de>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
Sjoerd Simons <sjoerd.simons@...labora.co.uk>
Subject: Re: [PATCH] [BUG] clk: rockchip: don't mark clock names as initconst
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 new elements into separate entities, which can have
> > __initdata attributes again.
> >
> >
> > Heiko
> >
> > [0] http://www.spinics.net/lists/arm-kernel/msg471295.html
>
> The patch looks good, but for some reason, the next-20151223 kernel had no
> problem and next-20151231 was broken, the top commits in
> drivers/clk/rockchips are:
That is correct. next-20151223 did not contain the offending patches yet.
After the patches got merged into the clock-tree the kbuild-robot alerted us
to the __initdata issue, so I created the linked patch as fixup.
Heiko
>
> commit a915e30dd26ea5f3cc2e2c044aba38ee5973d3fa
> Merge: ce6dd266d535 b0158bb27c7b
> Author: Michael Turquette <mturquette@...libre.com>
> Date: Wed Dec 23 13:08:56 2015 -0800
>
> Merge branch 'clk-rockchip' into clk-next
>
> commit b0158bb27c7b6e9843f541c17b24dbd964b76db6
> Author: Xing Zheng <zhengxing@...k-chips.com>
> Date: Tue Dec 22 22:28:01 2015 +0100
>
> clk: rockchip: rk3036: include downstream muxes into fractional dividers
>
> Use the newly introduced possibility to combine the fractional dividers
>
>
> Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists