public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"arm@kernel.org" <arm@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Mark Rutland <mark.rutland@arm.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Barry Song <baohua.song@csr.com>,
	Daniel Walker <dwalker@fifo99.com>,
	Bryan Huntsman <bryanh@codeaurora.org>,
	Tony Lindgren <tony@atomide.com>,
	John Stultz <john.stultz@linaro.org>,
	"Brown, David" <davidb@quicinc.com>
Subject: Re: [PATCHv4 00/11] Remove ARM local timer API
Date: Thu, 18 Apr 2013 09:39:09 -0700	[thread overview]
Message-ID: <20130418163909.GH7083@quad.lixom.net> (raw)
In-Reply-To: <516F09AA.2000902@codeaurora.org>

On Wed, Apr 17, 2013 at 01:44:26PM -0700, Stephen Boyd wrote:
> Thomas,
> 
> Would you be able to pick up patches 1 and 2 from this series and
> publish it as a stable branch? Preferably based on rc5 but I can always
> merge it to rc5 and apply the rest of the patches.
> 
> Arnd/Olof,
> 
> Would you be able to merge in the rest of the patches to arm-soc? I can
> provide a branch on 3.9-rc5 and a merge resolution with for-next in
> arm-soc that you can pull to look at.
> 
> If not I will have to resend the series.

Hi,

I think this is 3.11 material at this point, so please send a fresh pull
request (or re-ask us to apply it) after -rc1.


-Olof

      reply	other threads:[~2013-04-18 16:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 21:27 [PATCHv4 00/11] Remove ARM local timer API Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 01/11] clockevents: Prefer CPU local devices over global devices Stephen Boyd
2013-04-09 10:33   ` Mark Rutland
2013-04-09 16:49     ` Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 02/11] clocksource: add generic dummy timer driver Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 03/11] ARM: smp: Remove duplicate dummy timer implementation Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 04/11] ARM: smp_twd: Divorce smp_twd from local timer API Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 05/11] ARM: OMAP2+: Divorce " Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 06/11] ARM: EXYNOS4: Divorce mct " Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 07/11] ARM: PRIMA2: Divorce timer-marco " Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 08/11] ARM: msm: Divorce msm_timer " Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 09/11] clocksource: time-armada-370-xp: Fix sparse warning Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 10/11] clocksource: time-armada-370-xp: Divorce from local timer API Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 11/11] ARM: smp: Remove " Stephen Boyd
2013-04-17 20:44 ` [PATCHv4 00/11] Remove ARM " Stephen Boyd
2013-04-18 16:39   ` Olof Johansson [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=20130418163909.GH7083@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=baohua.song@csr.com \
    --cc=bryanh@codeaurora.org \
    --cc=davidb@quicinc.com \
    --cc=dwalker@fifo99.com \
    --cc=john.stultz@linaro.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=sboyd@codeaurora.org \
    --cc=tglx@linutronix.de \
    --cc=tony@atomide.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