linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 6/6] omap soc changes for v3.13 merge window
Date: Mon, 14 Oct 2013 15:45:12 -0700	[thread overview]
Message-ID: <8761sz4glj.fsf@linaro.org> (raw)
In-Reply-To: <5258a9ab.e703310a.12ff.2a82SMTPIN_ADDED_MISSING@mx.google.com> (Tony Lindgren's message of "Fri, 11 Oct 2013 18:44:59 -0700")

Tony Lindgren <tony@atomide.com> writes:

> The following changes since commit d0e639c9e06d44e713170031fe05fb60ebe680af:
>
>   Linux 3.12-rc4 (2013-10-06 14:00:20 -0700)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.13/soc-take2
>
> for you to fetch changes up to d5da94b88efebc375bfcbab6bb0e59a6e8a6571e:
>
>   ARM: OMAP2+: Fix build error for realtime counter init if not enabled (2013-10-11 17:28:04 -0700)
>
> ----------------------------------------------------------------
> SoC related changes for omaps to support the realtime
> counter on newer omaps, and to fail early for omap5 es1.0
> SoCs that don't have any support merged for them in the
> mainline tree.
>
> ----------------------------------------------------------------

Pulled into next/soc,

Thanks,

Kevin

       reply	other threads:[~2013-10-14 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5258a9ab.e703310a.12ff.2a82SMTPIN_ADDED_MISSING@mx.google.com>
2013-10-14 22:45 ` Kevin Hilman [this message]
2013-10-12  1:44 [GIT PULL 1/6] omap non-urgent fixes for v3.13 merge window Tony Lindgren
2013-10-12  1:44 ` [GIT PULL 6/6] omap soc changes " Tony Lindgren

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=8761sz4glj.fsf@linaro.org \
    --to=khilman@linaro.org \
    --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).