Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1205646 > unrolled thread

linux-next: build failure after merge of the clk tree

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2015-08-12 09:20 +0200
Last post2015-08-12 10:10 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.kernel


Contents

  linux-next: build failure after merge of the clk tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-08-12 09:20 +0200
    Re: linux-next: build failure after merge of the clk tree Geert Uytterhoeven <geert@linux-m68k.org> - 2015-08-12 09:50 +0200
      Re: linux-next: build failure after merge of the clk tree Stephen Boyd <sboyd@codeaurora.org> - 2015-08-12 10:30 +0200
    Re: linux-next: build failure after merge of the clk tree Stephen Boyd <sboyd@codeaurora.org> - 2015-08-12 10:10 +0200

#1205646 — linux-next: build failure after merge of the clk tree

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2015-08-12 09:20 +0200
Subjectlinux-next: build failure after merge of the clk tree
Message-ID<pWyun-5LM-41@gated-at.bofh.it>
Hi all,

After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

ERROR: "pm_genpd_init" [drivers/clk/qcom/clk-qcom.ko] undefined!

Caused by commit

  0c4172846b0b ("clk: qcom: Add support for GDSCs")

I have used the clk tree from next-20150810 for today.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1205672

FromGeert Uytterhoeven <geert@linux-m68k.org>
Date2015-08-12 09:50 +0200
Message-ID<pWyXn-6k2-1@gated-at.bofh.it>
In reply to#1205646
On Wed, Aug 12, 2015 at 9:19 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: "pm_genpd_init" [drivers/clk/qcom/clk-qcom.ko] undefined!
>
> Caused by commit
>
>   0c4172846b0b ("clk: qcom: Add support for GDSCs")
>
> I have used the clk tree from next-20150810 for today.

Missing EXPORT_SYMBOL_GPL(pm_genpd_init)?

However, having modular PM Domain drivers may cause unpleasant surprises...

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1205696

FromStephen Boyd <sboyd@codeaurora.org>
Date2015-08-12 10:30 +0200
Message-ID<pWzA6-7iu-17@gated-at.bofh.it>
In reply to#1205672
On 08/12, Geert Uytterhoeven wrote:
> On Wed, Aug 12, 2015 at 9:19 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > ERROR: "pm_genpd_init" [drivers/clk/qcom/clk-qcom.ko] undefined!
> >
> > Caused by commit
> >
> >   0c4172846b0b ("clk: qcom: Add support for GDSCs")
> >
> > I have used the clk tree from next-20150810 for today.
> 
> Missing EXPORT_SYMBOL_GPL(pm_genpd_init)?
> 
> However, having modular PM Domain drivers may cause unpleasant surprises...
> 

Curious what sort of surprises those would be? I suppose
something like power domains being removed from the system would
need some more work to start failing the suspend/resume of
devices in the power domains or possibly unbind the drivers that
are using the power domains provided. And we probably need to
sprinkle some try_module_get()/module_put() too so that the
module isn't easily removed if it's in use by some other drivers.

I hope it's not something that we think is impossible to do
though because we've been able to support the clk driver as
entirely modular on qcom platforms and I'd like to keep it that
way. BTW, it seems that we export __of_genpd_add_provider() so
there's at least some precedence for modular genpd code, albeit a
small one.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1205684

FromStephen Boyd <sboyd@codeaurora.org>
Date2015-08-12 10:10 +0200
Message-ID<pWzgK-6VW-21@gated-at.bofh.it>
In reply to#1205646
On 08/12, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> ERROR: "pm_genpd_init" [drivers/clk/qcom/clk-qcom.ko] undefined!
> 
> Caused by commit
> 
>   0c4172846b0b ("clk: qcom: Add support for GDSCs")
> 
> I have used the clk tree from next-20150810 for today.

Thanks. I've removed these patches from the clk tree until this
is resolved.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web