From: Mike Turquette <mturquette@linaro.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH V2 0/2] clk: shmobile: clk-mstp fixes
Date: Tue, 14 Jan 2014 19:44:41 +0000 [thread overview]
Message-ID: <20140114194441.7168.37136@quantum> (raw)
In-Reply-To: <1388232549-6740-1-git-send-email-valentine.barshak@cogentembedded.com>
Quoting Simon Horman (2014-01-09 17:07:01)
> [ CC Ben Dooks ]
>
> On Mon, Jan 06, 2014 at 08:33:17PM +0400, Valentine wrote:
> > On 12/30/2013 01:54 AM, Mike Turquette wrote:
> > >Quoting Valentine Barshak (2013-12-28 04:09:07)
> > >>This fixes a number of issues with CPG MSTP clock array handling.
> > >
> > >Thanks for the quick respin. Taken into clk-next.
> >
> > Sorry, I don't see it in https://git.linaro.org/people/mike.turquette/linux.git/shortlog/refs/heads/clk-next
> > Is this the right place to look for?
>
> Hi Mike,
>
> I'm not seeing them there either.
>
> Also, I would like to pull these changes into my "devel" branch
> as they fix problems that developers are hitting. If I could use
> an updated clk-next-shmobile branch that includes these patches
> and commit ids that won't change I would be most grateful.
Hi all,
Thanks for your persistence. This was sitting in a local branch for a
while and I forgot to merge it into clk-next. I've updated the
clk-next-shmobile branch to include these patches and I have applied all
Acks and Tested-bys. That branch includes some other patches as well but
it shouldn't be a problem for a development branch.
I've also merged clk-next-shmobile into clk-next and pushed out to my
Linaro mirror.
Regards,
Mike
>
> Thanks.
next prev parent reply other threads:[~2014-01-14 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 12:09 [PATCH V2 0/2] clk: shmobile: clk-mstp fixes Valentine Barshak
2013-12-29 21:54 ` Mike Turquette
2014-01-06 16:33 ` Valentine
2014-01-10 1:07 ` Simon Horman
2014-01-14 18:41 ` Ben Dooks
2014-01-14 18:54 ` Ben Dooks
2014-01-14 19:44 ` Mike Turquette [this message]
2014-01-14 19:57 ` Ben Dooks
2014-01-15 0:25 ` Simon Horman
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=20140114194441.7168.37136@quantum \
--to=mturquette@linaro.org \
--cc=linux-sh@vger.kernel.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).