public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jason Cooper <jason@lakedaemon.net>,
	Olof Johansson <olof@lixom.net>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [GIT PULL] clockevents/clocksource : armada-370-xp fixes, sh_cmt, em_sti  timer-sp and nomadik changes
Date: Wed, 11 Sep 2013 14:45:02 -0300	[thread overview]
Message-ID: <20130911174501.GA11003@localhost> (raw)
In-Reply-To: <5224EEB4.2080902@linaro.org>

Hi Thomas, Daniel,

On Mon, Sep 02, 2013 at 10:01:56PM +0200, Daniel Lezcano wrote:
[..]
> 
> The following changes since commit cfb6d656d569510ac9239583ce09e4c92ad54719:
> 
>   Merge branch 'timers/clockevents-next' of
> git://git.linaro.org/people/dlezcano/clockevents into timers/core
> (2013-08-21 14:59:23 +0200)
> 
> are available in the git repository at:
> 
> 
>   git://git.linaro.org/people/dlezcano/clockevents.git timers/clockevents
> 
> for you to fetch changes up to 63ce2cc474ce962d936ae6dfaa6ae2354b1db5b2:
> 
>   clocksource: armada-370-xp: Add detailed clock requirements in
> devicetree binding (2013-09-02 21:44:58 +0200)
> 

I've seen Ingo's timer pull on September 3rd, so I'm pretty
sure this late pull won't make it for v3.12.

Can you confirm this?
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

      reply	other threads:[~2013-09-11 17:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 20:01 [GIT PULL] clockevents/clocksource : armada-370-xp fixes, sh_cmt, em_sti timer-sp and nomadik changes Daniel Lezcano
2013-09-11 17:45 ` Ezequiel Garcia [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=20130911174501.GA11003@localhost \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=andrew@lunn.ch \
    --cc=daniel.lezcano@linaro.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@free-electrons.com \
    /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