From: Mike Turquette <mturquette@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>, Kumar Gala <galak@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] qcom clock changes for 3.17
Date: Mon, 28 Jul 2014 14:13:57 -0700 [thread overview]
Message-ID: <20140728211357.4906.1815@quantum> (raw)
In-Reply-To: <20140728175702.GB19933@codeaurora.org>
Quoting Stephen Boyd (2014-07-28 10:57:02)
> On 07/28, Kumar Gala wrote:
> >
> > On Jul 21, 2014, at 4:26 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> >
> > > Hi Mike,
> > >
> > > The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
> > >
> > > Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
> > >
> > > are available in the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git tags/qcom-clocks-for-3.17
> > >
> > > for you to fetch changes up to e216ce60a9e05ab399d098f05cd86fd95c9da8d5:
> > >
> > > clk: qcom: Add support for APQ8064 multimedia clocks (2014-07-15 16:39:03 -0700)
> >
> > Mike,
> >
> > Any update on this pull request?
> >
>
> I think Mike picked it up already but I don't see it pushed out
> to clk-next so far.
Stephen is correct. I'll push out the latest commits later today.
Regards,
Mike
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] qcom clock changes for 3.17
Date: Mon, 28 Jul 2014 14:13:57 -0700 [thread overview]
Message-ID: <20140728211357.4906.1815@quantum> (raw)
In-Reply-To: <20140728175702.GB19933@codeaurora.org>
Quoting Stephen Boyd (2014-07-28 10:57:02)
> On 07/28, Kumar Gala wrote:
> >
> > On Jul 21, 2014, at 4:26 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> >
> > > Hi Mike,
> > >
> > > The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
> > >
> > > Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
> > >
> > > are available in the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git tags/qcom-clocks-for-3.17
> > >
> > > for you to fetch changes up to e216ce60a9e05ab399d098f05cd86fd95c9da8d5:
> > >
> > > clk: qcom: Add support for APQ8064 multimedia clocks (2014-07-15 16:39:03 -0700)
> >
> > Mike,
> >
> > Any update on this pull request?
> >
>
> I think Mike picked it up already but I don't see it pushed out
> to clk-next so far.
Stephen is correct. I'll push out the latest commits later today.
Regards,
Mike
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> hosted by The Linux Foundation
next prev parent reply other threads:[~2014-07-28 21:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 21:26 [GIT PULL] qcom clock changes for 3.17 Stephen Boyd
2014-07-21 21:26 ` Stephen Boyd
2014-07-25 23:14 ` Mike Turquette
2014-07-25 23:14 ` Mike Turquette
2014-07-28 15:33 ` Kumar Gala
2014-07-28 15:33 ` Kumar Gala
2014-07-28 17:57 ` Stephen Boyd
2014-07-28 17:57 ` Stephen Boyd
2014-07-28 21:13 ` Mike Turquette [this message]
2014-07-28 21:13 ` Mike Turquette
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=20140728211357.4906.1815@quantum \
--to=mturquette@linaro.org \
--cc=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.