linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/6] clk: samsung: move common plls registration into separate function
Date: Fri, 02 Aug 2013 14:35:16 -0700	[thread overview]
Message-ID: <20130802213516.6450.7848@quantum> (raw)
In-Reply-To: <201307111052.13618.heiko@sntech.de>

Quoting Heiko St?bner (2013-07-11 01:52:13)
> Am Donnerstag, 11. Juli 2013, 09:46:53 schrieb Tomasz Figa:
> > Hi,
> > 
> > On Wednesday 10 of July 2013 22:29:13 Yadwinder Singh Brar wrote:
> > > Hi Heiko,
> > > 
> > > On Wed, Jul 10, 2013 at 4:27 AM, Heiko St?bner <heiko@sntech.de> wrote:
> > > > All Samsung PLLs use similar code to register the clocks and clkdev
> > > > lookups. Therefore move these into a separate function to reduce code
> > > > duplication.
> > > > 
> > > > Suggested-by: Russell King <linux@arm.linux.org.uk>
> > > > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > > > ---
> > > 
> > > I have posted patch for adding common pll registration function
> > > which some how missed to get merged. I hope will get merged after rc1.
> > > Please give a look at that :
> > > http://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg19543.ht
> > > ml
> > 
> > Yeah, I was going to post a link to it, but I couldn't find it on any
> > mailing list archive. I think we should go with the way of registration
> > introduced by Yadwinder.
> 
> the linked patch looks nice, thanks for the link. So I'll redo the plls 
> against it in the next round.

I just took that series into clk-next, so you can base v2 of this series
against clk-next.

Regards,
Mike

> 
> 
> Heiko

  reply	other threads:[~2013-08-02 21:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 22:57 [PATCH v2 0/6] Convert S3C2416 ad S3C2443 to common clock framework Heiko Stübner
2013-07-09 22:57 ` [PATCH v2 1/6] clk: samsung: move common plls registration into separate function Heiko Stübner
2013-07-10 16:59   ` Yadwinder Singh Brar
2013-07-11  7:46     ` Tomasz Figa
2013-07-11  8:52       ` Heiko Stübner
2013-08-02 21:35         ` Mike Turquette [this message]
2013-07-09 22:58 ` [PATCH v2 2/6] clk: samsung: fix error handling in pll register functions Heiko Stübner
2013-07-11  7:50   ` Tomasz Figa
2013-07-09 22:59 ` [PATCH v2 3/6] clk: samsung: add plls used in s3c2416 and s3c2443 Heiko Stübner
2013-07-11  8:16   ` Tomasz Figa
2013-07-11  8:50     ` Heiko Stübner
2013-07-11  9:25       ` Tomasz Figa
2013-07-09 22:59 ` [PATCH v2 4/6] ARM: S3C24XX: enable legacy clock code only when SAMSUNG_CLOCK selected Heiko Stübner
2013-07-09 23:00 ` [PATCH v2 5/6] clk: samsung: add clock-driver for s3c2416, s3c2443 and s3c2450 Heiko Stübner
2013-07-11  9:13   ` Tomasz Figa
2013-07-09 23:00 ` [PATCH v2 6/6] ARM: S3C24XX: Convert s3c2416 and s3c2443 to common clock framework Heiko Stübner
2013-07-16  7:09   ` Kukjin Kim
2013-07-22 17:07     ` Tomasz Figa
2013-07-24 12:59       ` Kukjin Kim
2013-07-24 14:01         ` Tomasz Figa
2013-08-05 17:03       ` Kukjin Kim
2013-07-10  8:47 ` [PATCH v2 0/6] Convert S3C2416 ad S3C2443 " Thomas Abraham
2013-08-05 17:05 ` Kukjin Kim

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=20130802213516.6450.7848@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).