From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clockevents/clocksource: Add Marvell Orion SoC timer
Date: Tue, 16 Jul 2013 17:55:41 +0200 [thread overview]
Message-ID: <51E56CFD.9050508@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1307081041290.32106@ionos.tec.linutronix.de>
On 07/08/2013 10:45 AM, Thomas Gleixner wrote:
> On Sun, 7 Jul 2013, Jason Cooper wrote:
>> On Sun, Jul 07, 2013 at 05:30:31PM +0200, Thomas Gleixner wrote:
>> I don't mind delaying half of a series so the drivers/ portion can land
>> in mainline, and the rest can land in the next cycle. But when things
>> don't go according to that plan, I'd like a little consideration /
>> flexibility about solving the problem. Especially considering I'm
>> *trying* to do the right thing by pushing to appropriate maintainers
>> first.
>>
>> Of course, this is a moot point since, as you clarified above, this
>> dependency doesn't have the hazards typically associated with
>> out-of-tree dependencies.
>
> There is a very simple procedure for stuff like this.
>
> Series has parts which go through tree A and B and another larger part
> for tree C which depends on the A and B parts.
>
> So ask the maintainers of A and B to apply this to separate branches,
> which are based on some commit in Linus tree. These branches can be
> pulled into C and C can apply the depending stuff on top.
>
> Now the maintainers of A and B merge these branches into their main
> devel branch, can do further fixups and stuff on top. And the whole
> thing just works without glitches during the merge window.
>
> We do this all the time.
Ok, I was about to send to both of you a PR with a common ancestor [1]
for this patch but finally this patch has been taken for timers/urgent.
I don't have to send the PR, right ?
timers/urgent will be merged into timers/core, correct ?
Thanks
-- Daniel
[1]
https://git.linaro.org/gitweb?p=people/dlezcano/clockevents.git;a=shortlog;h=refs/heads/timers/mvebu-deps-3.12
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-07-16 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51B8D310.4050404@linaro.org>
2013-07-07 11:44 ` [GIT PULL] clockevents/clocksource: Add Marvell Orion SoC timer Sebastian Hesselbarth
2013-07-07 13:10 ` Thomas Gleixner
2013-07-07 14:46 ` Jason Cooper
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 [this message]
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=51E56CFD.9050508@linaro.org \
--to=daniel.lezcano@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).