From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] get rid of <mach/timex.h>
Date: Thu, 19 Dec 2013 07:20:42 -0800 [thread overview]
Message-ID: <87bo0clved.fsf@linaro.org> (raw)
In-Reply-To: <20131213221651.GA10344@perseus.defre.xn--kleine-knig-yfb.de> ("Uwe Kleine-König"'s message of "Fri, 13 Dec 2013 23:16:51 +0100")
Hi Uwe,
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix•de> writes:
> Hello,
>
> the following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
>
> Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
>
> are available in the git repository at:
>
> git://git.pengutronix.de/git/ukl/linux.git tags/dropmachtimexh
>
> for you to fetch changes up to c24eb46490c8232c08c82cd591ba332284d257b2:
>
> ARM: drop <mach/timex.h> for !ARCH_MULTIPLATFORM, too (2013-12-07 23:31:28 +0100)
>
> I'd like to get these changes into 3.14-rc1, so it would be great if you
> could take it into armsoc for some exposure into next.
>
> The kbuild test robot is happy with these changes, and I did several
> build tests, too, so I don't expect any breakage.
>
> Merging this series will result in a few merge conflicts. I pushed a
> branch dropmachtimexh-merged into my repository where you can see how I
> resolved them merging in current next/master into my tag.
I pulled this into our arm-soc/to-build for build and boot testing and
there was quite a few defconfigs that did not build (ignore the at91
failures, those are my fault):
http://lists.linaro.org/pipermail/kernel-build-reports/2013-December/001573.html
Looks like there are still several users of LATCH, which references CLOCK_TICK_RATE
and is causing failures on lots of defconfigs.
I tried a few of those same defconfig builds on your merged branch and
it has the same build failures.
Kevin
next prev parent reply other threads:[~2013-12-19 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 22:16 [GIT PULL] get rid of <mach/timex.h> Uwe Kleine-König
2013-12-17 13:28 ` Uwe Kleine-König
2013-12-19 15:20 ` Kevin Hilman [this message]
2013-12-19 21:57 ` [PATCH] ARM: rpc: stop using <mach/timex.h> Uwe Kleine-König
2013-12-19 22:17 ` [GIT PULL] get rid of <mach/timex.h> Uwe Kleine-König
2013-12-20 8:35 ` Linus Walleij
2013-12-20 13:20 ` Sascha Hauer
2013-12-20 18:47 ` Uwe Kleine-König
2014-01-07 11:24 ` Nicolas Ferre
2014-01-13 13:36 ` Linus Walleij
2014-01-13 18:26 ` Olof Johansson
2014-01-13 19:42 ` Uwe Kleine-König
2014-02-03 10:31 ` [PATCH] [RFC] ARM: ixp4xx: fix timer latch calculation Uwe Kleine-König
2014-02-17 7:43 ` Uwe Kleine-König
2014-01-14 10:25 ` [GIT PULL] get rid of <mach/timex.h> Linus Walleij
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=87bo0clved.fsf@linaro.org \
--to=khilman@linaro$(echo .)org \
--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