From: Arnd Bergmann <arnd@arndb.de>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Subject: Re: [PATCH] [BUG] clk: rockchip: don't mark clock names as initconst
Date: Fri, 01 Jan 2016 22:50:43 +0100 [thread overview]
Message-ID: <6692523.e5K11FUKe0@wuerfel> (raw)
In-Reply-To: <1799610.nrn5HMCSxL@diego>
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:
commit a915e30dd26ea5f3cc2e2c044aba38ee5973d3fa
Merge: ce6dd266d535 b0158bb27c7b
Author: Michael Turquette <mturquette@baylibre.com>
Date: Wed Dec 23 13:08:56 2015 -0800
Merge branch 'clk-rockchip' into clk-next
commit b0158bb27c7b6e9843f541c17b24dbd964b76db6
Author: Xing Zheng <zhengxing@rock-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
next prev parent reply other threads:[~2016-01-01 21:52 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
2016-01-01 21:50 ` Arnd Bergmann [this message]
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=6692523.e5K11FUKe0@wuerfel \
--to=arnd@arndb.de \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=sjoerd.simons@collabora.co.uk \
/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