From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] omap clock late patches for v3.7 merge window
Date: Mon, 24 Sep 2012 14:30:57 -0700 [thread overview]
Message-ID: <20120924213057.GM28835@atomide.com> (raw)
In-Reply-To: <pull-1348521952-285145>
* Tony Lindgren <tony@atomide.com> [120924 14:26]:
>
> These changes take us a step closer to merging the common clock
> framework for omap but unfortunately these patches were not
> ready for merging earlier. See also the notes below on the
> dependencies these patches have, they are based on a merge
> of sereral branches already merged.
I am aware these three pull requests all are very late.
Just let me know if you don't want to take them at this point
and I'll resend updated pull reqs after -rc1 or so.
Regards,
Tony
next prev parent reply other threads:[~2012-09-24 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 21:25 [GIT PULL 1/3] omap clock late patches for v3.7 merge window Tony Lindgren
2012-09-24 21:25 ` [GIT PULL 2/3] omap platform and board related " Tony Lindgren
2012-09-24 21:25 ` [GIT PULL 3/3] omap arch timer late changes " Tony Lindgren
2012-09-24 21:30 ` Tony Lindgren [this message]
[not found] ` <E1TGGAI-0000D1-T0@merlin.infradead.org>
2012-09-25 0:39 ` [GIT PULL 2/3] omap platform and board related late patches " Tony Lindgren
2012-09-25 3:31 ` Tony Lindgren
2012-09-29 21:03 ` Olof Johansson
2012-09-30 18:17 ` Tony Lindgren
[not found] ` <5060cfe6.8187e50a.7ef1.ffff8d51SMTPIN_ADDED@mx.google.com>
2012-09-29 20:58 ` [GIT PULL 3/3] omap arch timer late changes " Olof Johansson
[not found] <5060d05b.c787e50a.133c.67b1SMTPIN_ADDED@mx.google.com>
2012-09-29 20:57 ` [GIT PULL 1/3] omap clock late patches " Olof Johansson
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=20120924213057.GM28835@atomide.com \
--to=tony@atomide.com \
--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).