From: Shawn Guo <shawn.guo@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the imx-mxs tree
Date: Fri, 29 May 2015 21:16:55 +0800 [thread overview]
Message-ID: <20150529131654.GL16165@dragon> (raw)
In-Reply-To: <20150529212859.0acb08e2@canb.auug.org.au>
Hi Stephen,
On Fri, May 29, 2015 at 09:28:59PM +1000, Stephen Rothwell wrote:
> Hi Shawn,
>
> After merging the imx-mxs tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
>
> drivers/clocksource/timer-imx-gpt.c:37:27: fatal error: asm/mach/time.h: No such file or directory
> #include <asm/mach/time.h>
> ^
>
> Caused by commit 77b0235b6b5c ("ARM: imx: move timer driver into
> drivers/clocksource").
>
> I have marked it as BROKEN for now:
Thanks for the report. I just sent a fix for it, and will get it into
my for-next branch soon.
Sorry for the breakage.
Shawn
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri, 29 May 2015 21:24:03 +1000
> Subject: [PATCH] ARM: imx: mark CLKSRC_IMX_GPT as BROKEN for now
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/clocksource/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
> index 3c15a49fdac9..d8fedc925864 100644
> --- a/drivers/clocksource/Kconfig
> +++ b/drivers/clocksource/Kconfig
> @@ -279,6 +279,7 @@ config CLKSRC_PXA
> config CLKSRC_IMX_GPT
> bool "Clocksource using i.MX GPT" if COMPILE_TEST
> depends on OF
> + depends on BROKEN
> select CLKSRC_MMIO
>
> config H8300_TMR16
> --
> 2.1.4
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
next prev parent reply other threads:[~2015-05-29 13:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 11:28 linux-next: build failure after merge of the imx-mxs tree Stephen Rothwell
2015-05-29 13:16 ` Shawn Guo [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-01 12:35 Stephen Rothwell
2019-01-10 22:30 Stephen Rothwell
2019-01-10 22:56 ` Stephen Rothwell
2019-01-10 23:15 ` Lukasz Majewski
2019-01-12 1:23 ` Shawn Guo
2019-04-22 22:45 Stephen Rothwell
2019-04-22 22:54 ` Fabio Estevam
2019-04-23 2:12 ` Shawn Guo
2019-05-20 22:37 Stephen Rothwell
2019-05-21 2:16 ` Anson Huang
2019-05-21 4:43 ` Shawn Guo
2019-12-11 21:35 Stephen Rothwell
2019-12-12 1:33 ` Shawn Guo
2019-12-12 9:45 ` Lucas Stach
2019-12-12 11:37 ` Shawn Guo
2020-02-18 2:08 Stephen Rothwell
2020-02-18 2:18 ` Peng Fan
2020-02-18 9:38 ` Shawn Guo
2020-11-03 1:00 Stephen Rothwell
2020-11-03 6:39 ` Shawn Guo
2021-12-06 22:10 Stephen Rothwell
2021-12-07 7:27 ` Michal Vokáč
2022-10-30 22:09 Stephen Rothwell
2022-10-30 22:11 ` Alistair
2022-10-31 0:52 ` Shawn Guo
2023-03-07 1:31 Stephen Rothwell
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=20150529131654.GL16165@dragon \
--to=shawn.guo@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.