linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/3] clk: add clock-indices support
Date: Thu, 06 Mar 2014 19:05:40 +0000	[thread overview]
Message-ID: <5318C704.30108@codethink.co.uk> (raw)
In-Reply-To: <1392314571-30107-1-git-send-email-ben.dooks@codethink.co.uk>

On 23/02/14 23:46, Mike Turquette wrote:
> Quoting Laurent Pinchart (2014-02-23 14:40:46)
>> Hi Mike,
>>
>> On Sunday 23 February 2014 13:00:24 Mike Turquette wrote:
>>> Quoting Ben Dooks (2014-02-13 10:02:49)
>>>
>>>> Add a property called clock-indices to allow clock-output-names
>>>> to be used where the index used to lookup a clock is not a 1:1
>>>> mapping to the array position in the clock-output-names
>>>>
>>>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>>>
>>> Ben & Laurent,
>>>
>>> The clock-indices stuff looks sane to me. I've taken Ben's patch #1 into
>>> clk-next. It seems patch #3 might be dropped and patch #2 didn't apply
>>> cleanly for me.
>>>
>>> Can Laurent's patches and Ben's #2 be rebased and sent together as a PR?
>>
>> Sure. I've pushed my pending patches to
>>
>>          git://linuxtv.org/pinchartl/fbdev.git clocks/next/drivers
>>
>> Ben, could you please rebase your patch on top of it and repost ? I'll then
>> send a pull request to Mike.
>
> FYI, I've just pushed a new clk-next branch based on -rc3 out to my
> linaro remote. You don't need to rebase but it's there if you want to
> put your stuff on top of the latest.

Thanks. Will look at re-doing the reneasas clock driver as soon as
we can get some discussion on the best way to deal with the merging.


-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

      parent reply	other threads:[~2014-03-06 19:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 18:02 [PATCH 1/3] clk: add clock-indices support Ben Dooks
2014-02-13 18:08 ` Sergei Shtylyov
2014-02-13 18:08 ` Ben Dooks
2014-02-23 21:00 ` Mike Turquette
2014-02-23 22:40 ` Laurent Pinchart
2014-02-24  0:29 ` Laurent Pinchart
2014-03-02 22:28 ` Ben Dooks
2014-03-02 22:37 ` Laurent Pinchart
2014-03-02 22:52 ` Ben Dooks
2014-03-06 19:05 ` Ben Dooks [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=5318C704.30108@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --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).