From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] clk: pxa clocks build system fix
Date: Mon, 06 Oct 2014 23:36:43 +0200 [thread overview]
Message-ID: <7069544.aUPivvE1xF@wuerfel> (raw)
In-Reply-To: <8761fwc2me.fsf@free.fr>
On Monday 06 October 2014 23:25:13 Robert Jarzmik wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
>
> > On Sunday 05 October 2014 13:43:58 Mike Turquette wrote:
> >> Quoting Robert Jarzmik (2014-10-01 14:39:29)
> >> > Fix the building of pxa clock drivers so that the files are actually
> >> > compiled if and only if COMMON_CLK was selected by the architecture.
> >> >
> >> > This prevents conflicts with mach-pxa clock legacy implementation.
> >> >
> >> > Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
> >>
> >
> > I seem to still hit a build error with this applied in e.g.
> > build/palmz72_defconfig, which enables both pxa25x and pxa27x,
> > so I get both the pxa250 private clock code and the pxa270
> > common clock code, resulting in this error message:
> Do you have the patch "Revert "arm: pxa: Transition pxa27x to clk framework" in
> your tree ?
>
> Normally the fix was made of :
> - the fixup patch "clk: pxa clocks build system fix"
> - the revert queued by Mike "arm: pxa: Transition pxa27x to clk framework"
No, I was missing that one, sorry for the noise. It works now after
I've applied it. I was using the latest -next kernel as a base and assumed
that it had all the latest fixes from Mike's tree.
Arnd
next prev parent reply other threads:[~2014-10-06 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 21:39 [PATCH v1] clk: pxa clocks build system fix Robert Jarzmik
2014-10-05 20:43 ` Mike Turquette
2014-10-06 20:35 ` Arnd Bergmann
2014-10-06 21:25 ` Robert Jarzmik
2014-10-06 21:36 ` Arnd Bergmann [this message]
2014-10-06 22:15 ` Mike Turquette
2014-10-07 9:12 ` Arnd Bergmann
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=7069544.aUPivvE1xF@wuerfel \
--to=arnd@arndb.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