From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: Timer build warnings fixes for v3.8-rc
Date: Fri, 14 Dec 2012 09:12:35 -0800 [thread overview]
Message-ID: <20121214171235.GN4989@atomide.com> (raw)
In-Reply-To: <50CB57AB.8080503@ti.com>
* Jon Hunter <jon-hunter@ti.com> [121214 08:48]:
> The following changes since commit 698d601224824bc1a5bf17f3d86be902e2aabff0:
>
> Merge tag 'drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2012-12-13 10:59:11 -0800)
>
> are available in the git repository at:
>
>
> git://github.com/jonhunter/linux.git fixes-timer-build
>
> for you to fetch changes up to bf85f205d95eb223e849914101e0db1a5a576a3c:
>
> ARM: OMAP2+: Fix sparse warnings in timer.c (2012-12-14 10:14:55 -0600)
>
> ----------------------------------------------------------------
> Fixes for a few timer warnings observed with different kernel
> configurations for OMAP2+ devices.
>
> I have dropped the patch to fix a build error for OMAP4 in the
> timer code as Olof already has this fix merged.
Thanks pulling into omap-for-v3.8/fixes-for-merge-window.
Regards,
Tony
> ----------------------------------------------------------------
>
> Jon Hunter (2):
> ARM: OMAP2+: Fix realtime_counter_init warning in timer.c
> ARM: AM335x: Fix warning in timer.c
>
> Vaibhav Hiremath (1):
> ARM: OMAP2+: Fix sparse warnings in timer.c
>
> arch/arm/mach-omap2/Kconfig | 3 ++-
> arch/arm/mach-omap2/timer.c | 6 +++---
> 2 files changed, 5 insertions(+), 4 deletions(-)
prev parent reply other threads:[~2012-12-14 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 16:45 [GIT PULL] ARM: OMAP2+: Timer build warnings fixes for v3.8-rc Jon Hunter
2012-12-14 17:12 ` Tony Lindgren [this message]
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=20121214171235.GN4989@atomide.com \
--to=tony@atomide.com \
--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;
as well as URLs for NNTP newsgroup(s).