From: Stephen Boyd <sboyd@codeaurora.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: Mike Turquette <mturquette@baylibre.com>,
"tony@atomide.com" <tony@atomide.com>,
Paul Walmsley <paul@pwsan.com>,
linux-clk@vger.kernel.org,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL]
Date: Wed, 15 Jul 2015 14:05:13 -0700 [thread overview]
Message-ID: <20150715210513.GR30412@codeaurora.org> (raw)
In-Reply-To: <55A6494F.7090508@ti.com>
On 07/15, Tero Kristo wrote:
> Hi Stephen, Mike,
>
> Here is the updated pull-request based on Stephen's request. This is
> on top of 4.1-rc2. The branch is force updated version of the one
> Stephen tried yesterday, the old one contained the minor build
> issues present on v3 of the patch set.
>
> I did a quick try of merging this branch on top of 4.2-rc2 and it
> works fine without any conflicts.
>
Thanks. Pulled into clk-next.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-07-15 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 11:51 [GIT PULL] Tero Kristo
2015-07-15 21:05 ` Stephen Boyd [this message]
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=20150715210513.GR30412@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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