From: Jason Cooper <jason@lakedaemon.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
John Stultz <john.stultz@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] clockevents/clocksource: Add Marvell Orion SoC timer
Date: Sun, 7 Jul 2013 10:46:45 -0400 [thread overview]
Message-ID: <20130707144645.GA11908@titan.lakedaemon.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1307071508030.32106@ionos.tec.linutronix.de>
Thomas,
On Sun, Jul 07, 2013 at 03:10:25PM +0200, Thomas Gleixner wrote:
> On Sun, 7 Jul 2013, Sebastian Hesselbarth wrote:
> > > ----------------------------------------------------------------
> > > Sebastian Hesselbarth (1):
> > > clocksource: Add Marvell Orion SoC timer
> >
> > with tip timers/core PR sent, I realized that the above did not make it
> > in. As we have a whole bunch of cleanup and DT conversion patches for
>
> Opps. Fell through the cracks.
No problem.
> > v3.11-rc1 depending on it, would it be ok for you to let Jason Cooper
> > take it through his ARM sub-branch?
>
> > If you are fine with it, I will resend the patch and note that Daniel
> > can drop it and Jason will take it.
>
> Nah, Jason can just pull it from Daniels tree and be done with it.
Sure, but to be clear, Daniel, please drop this patch from your tree. I
have no desire to create an out-of-tree dependency if we can avoid it.
It has a habit of going horribly wrong [1].
I'll cherry-pick
0c1dcfd clocksource: Add Marvell Orion SoC timer
from dlezcano/timers/clockevents to get the Signed-off-by's Tested-by's,
etc. If I could get an Acked-by from Daniel or Thomas on this, I'd
appreciate it.
Daniel, it looks like you only have cpuidle work going into linux-next.
If you do decide to include timers/clockevents, please drop the patch
before hand.
thx,
Jason.
[1] https://lkml.org/lkml/2013/2/28/725
next prev parent reply other threads:[~2013-07-07 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 19:59 Daniel Lezcano
2013-07-07 11:44 ` Sebastian Hesselbarth
2013-07-07 13:10 ` Thomas Gleixner
2013-07-07 14:46 ` Jason Cooper [this message]
2013-07-07 15:30 ` Thomas Gleixner
2013-07-07 16:45 ` Daniel Lezcano
2013-07-08 0:04 ` Jason Cooper
2013-07-07 23:58 ` Jason Cooper
2013-07-08 8:45 ` Thomas Gleixner
2013-07-08 15:28 ` managing out-of-tree deps for arm-soc in a single window was: " Jason Cooper
2013-07-16 15:55 ` Daniel Lezcano
2013-07-24 19:49 ` Jason Cooper
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=20130707144645.GA11908@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andrew@lunn.ch \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--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®