From: Scott Wood <scottwood@freescale.com>
To: Kevin Hao <haokexin@gmail.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Gerhard Sittig <gsi@denx.de>,
Yuantian Tang <Yuantian.Tang@freescale.com>,
Jingchang Lu <jingchang.lu@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 1/3] Revert "clk: ppc-corenet: Fix Section mismatch warning"
Date: Thu, 4 Dec 2014 21:51:59 -0600 [thread overview]
Message-ID: <1417751519.334.9.camel@freescale.com> (raw)
In-Reply-To: <1417596833-31456-2-git-send-email-haokexin@gmail.com>
On Wed, 2014-12-03 at 16:53 +0800, Kevin Hao wrote:
> This reverts commit da788acb28386aa896224e784954bb73c99ff26c.
>
> That commit tried to fix the section mismatch warning by moving the
> ppc_corenet_clk_driver struct to init section. This is definitely wrong
> because the kernel would free the memories occupied by this struct
> after boot while this driver is still registered in the driver core.
> The kernel would panic when accessing this driver struct.
>
> Cc: stable@vger.kernel.org # 3.17
> Signed-off-by: Kevin Hao <haokexin@gmail.com>
> Acked-by: Scott Wood <scottwood@freescale.com>
> Acked-by: Michael Turquette <mturquette@linaro.org>
> ---
> v3: Cc stable and add ack.
>
> v2: A new patch in v2.
>
> drivers/clk/clk-ppc-corenet.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/clk-ppc-corenet.c b/drivers/clk/clk-ppc-corenet.c
> index b6e6c85507a5..0a47d6f49cd6 100644
> --- a/drivers/clk/clk-ppc-corenet.c
> +++ b/drivers/clk/clk-ppc-corenet.c
> @@ -291,7 +291,7 @@ static const struct of_device_id ppc_clk_ids[] __initconst = {
> {}
> };
>
> -static struct platform_driver ppc_corenet_clk_driver __initdata = {
> +static struct platform_driver ppc_corenet_clk_driver = {
> .driver = {
> .name = "ppc_corenet_clock",
> .of_match_table = ppc_clk_ids,
This patch is going to conflict with commit a4ae8f3b0f7ac6ab3 "clk: drop
owner assignment from platform_drivers" in linux-next -- or rather,
you've based this on that patch, but it's not in mpe's next branch, so I
get a merge conflict and there'd be another merge conflict later on to
get back to the newer base.
I really think this should go via the clock tree. That's where the
breakage was introduced in the first place...
-Scott
next prev parent reply other threads:[~2014-12-05 3:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 8:53 [PATCH v3 0/3] fix a kernel panic on fsl corenet board when CONFIG_CLK_PPC_CORENET is enabled Kevin Hao
2014-12-03 8:53 ` [PATCH v3 1/3] Revert "clk: ppc-corenet: Fix Section mismatch warning" Kevin Hao
2014-12-04 4:04 ` Scott Wood
2014-12-04 4:38 ` Kevin Hao
2014-12-04 4:46 ` Scott Wood
2014-12-04 6:06 ` Kevin Hao
2014-12-05 1:10 ` Scott Wood
2014-12-05 3:51 ` Scott Wood [this message]
2014-12-09 1:34 ` Kevin Hao
2015-01-17 19:32 ` Mike Turquette
2015-01-15 2:50 ` Yuantian Tang
2014-12-03 8:53 ` [PATCH v3 2/3] powerpc: call of_clk_init() from time_init() Kevin Hao
2014-12-03 8:53 ` [PATCH v3 3/3] clk: ppc-corenet: fix section mismatch warning Kevin Hao
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=1417751519.334.9.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Yuantian.Tang@freescale.com \
--cc=gsi@denx.de \
--cc=haokexin@gmail.com \
--cc=jingchang.lu@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mturquette@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.