linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 23:05:10 +0100	[thread overview]
Message-ID: <3926467.jaQRQH5bEO@diego> (raw)
In-Reply-To: <6692523.e5K11FUKe0@wuerfel>

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@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

  reply	other threads:[~2016-01-01 22:05 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
2016-01-01 22:05     ` Heiko Stübner [this message]
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=3926467.jaQRQH5bEO@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).