From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clk: mvebu: for v3.14
Date: Fri, 20 Dec 2013 13:27:33 -0800 [thread overview]
Message-ID: <20131220212733.18119.14852@quantum> (raw)
In-Reply-To: <20131220011521.GA9710@localhost>
Quoting Ezequiel Garcia (2013-12-19 17:15:22)
> On Wed, Dec 11, 2013 at 12:49:35PM -0500, Jason Cooper wrote:
> > On Fri, Dec 06, 2013 at 11:26:58AM -0500, Jason Cooper wrote:
> > > On Sun, Dec 01, 2013 at 12:07:52PM -0500, Jason Cooper wrote:
> > > > Mike,
> > > >
> > > > Here's the first round for v3.14. These have been in -next for a week
> > > > now, without problem.
> > >
> > > Ping? I see you've been pulling stuff into your -next branch. Did you
> > > miss this, or did I send it to the wrong list?
> >
> > re-ping?
> >
>
> Any news on this? Is there any problem with this driver?
Taken into clk-next.
Thanks!
Mike
> --
> Ezequiel Garc?a, Free Electrons
> Embedded Linux, Kernel and Android Engineering
> http://free-electrons.com
next prev parent reply other threads:[~2013-12-20 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 17:07 [GIT PULL] clk: mvebu: for v3.14 Jason Cooper
2013-12-06 16:26 ` Jason Cooper
2013-12-11 17:49 ` Jason Cooper
2013-12-20 1:15 ` Ezequiel Garcia
2013-12-20 21:27 ` Mike Turquette [this message]
2013-12-20 21:35 ` Ezequiel Garcia
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=20131220212733.18119.14852@quantum \
--to=mturquette@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