devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette-l0cyMroinI0@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Gregory CLEMENT
	<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: Thomas Petazzoni
	<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/1] clk: add DT fixed-factor-clock binding support
Date: Thu, 06 Sep 2012 17:08:19 -0700	[thread overview]
Message-ID: <20120907000819.20289.87301@nucleus> (raw)
In-Reply-To: <5048CC37.6060509-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Quoting Rob Herring (2012-09-06 09:15:51)
> On 08/28/2012 05:53 PM, Gregory CLEMENT wrote:
> > Hi,
> > 
> > During the port of the clock common framework for the armada 370/XP, I
> > need to get "fixed-factor-clock" using the device tree. For this need
> > I add support DT for "fixed-factor-clock" in the same way that the
> > existing support for "fixed-rate-clock". It turned out that finally I
> > didn't need it anymore, but as the code was written and tested, here
> > it is.
> > 
> 
> It looks fine to me, but I'd like to see a user of it.
> 

Agreed.  I'll hold off on merging it until someone else depends on it.

Thanks for submitting this Gregory.

Regards,
Mike

> Rob

      parent reply	other threads:[~2012-09-07  0:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 22:53 [PATCH 0/1] clk: add DT fixed-factor-clock binding support Gregory CLEMENT
2012-08-28 22:53 ` [PATCH] " Gregory CLEMENT
     [not found] ` <1346194382-11405-1-git-send-email-gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2012-09-06 16:15   ` [PATCH 0/1] " Rob Herring
     [not found]     ` <5048CC37.6060509-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-09-07  0:08       ` Mike Turquette [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=20120907000819.20289.87301@nucleus \
    --to=mturquette-l0cymroini0@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.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).