mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: arm@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Russell King <rmk@arm.linux.org.uk>,
	David Brown <davidb@codeaurora.org>,
	Barry Song <baohua.song@csr.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Remove ARM local timer API
Date: Thu, 27 Jun 2013 17:08:53 -0700	[thread overview]
Message-ID: <20130628000853.GB11547@quad.lixom.net> (raw)
In-Reply-To: <20130625200211.GA11625@codeaurora.org>

On Tue, Jun 25, 2013 at 01:02:12PM -0700, Stephen Boyd wrote:
> Olof/Arnd,
> 
> These patches remove the ARM local timer API. The ARM architected
> timers have already moved away from this API so this series
> migrates the rest of the users allowing us to remove the API
> entirely. Thomas has been kind enough to take the first two
> patches into timers/core in the tip tree (thanks Thomas!) so I've
> merged that into v3.10-rc1 and then applied the rest of the
> patches on top. Let me know if this is acceptable.

We need guarantees from Thomas that the branch is stable and will never be
rebased before it hit Linus tree, or we'll be in a world of pain for
dependencies like these.

Thomas, is this branch stable or do you anticipate a rebase?


-Olof

  parent reply	other threads:[~2013-06-28  0:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 20:02 Stephen Boyd
2013-06-26  1:06 ` Barry Song
2013-06-28  0:08 ` Olof Johansson [this message]
2013-07-08 15:35   ` Stephen Boyd
2013-07-17 21:52     ` Stephen Boyd
2013-07-19  7:24       ` Olof Johansson
2013-07-23 22:10 ` Olof Johansson
2013-07-23 23:40   ` Stephen Boyd
2013-07-23 23:56     ` Olof Johansson
2013-07-25 16:13       ` Stephen Boyd

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=20130628000853.GB11547@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=baohua.song@csr.com \
    --cc=davidb@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=sboyd@codeaurora.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®