public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v1] clk: pxa clocks build system fix
Date: Mon, 06 Oct 2014 23:25:13 +0200	[thread overview]
Message-ID: <8761fwc2me.fsf@free.fr> (raw)
In-Reply-To: <2017199.vcTs1JkoqL@wuerfel> (Arnd Bergmann's message of "Mon, 06 Oct 2014 22:35:26 +0200")

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"

Cheers.

--
Robert

  reply	other threads:[~2014-10-06 21:25 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 [this message]
2014-10-06 21:36       ` Arnd Bergmann
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=8761fwc2me.fsf@free.fr \
    --to=robert.jarzmik@free$(echo .)fr \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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