All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [GIT PULL] rockchip clock changes for 4.7 part 4 - some more fixes
Date: Mon, 9 May 2016 16:05:16 -0700	[thread overview]
Message-ID: <20160509230516.GB3492@codeaurora.org> (raw)
In-Reply-To: <16076636.fp1YCeqDWQ@phil>

On 05/09, Heiko Stübner wrote:
> Hi Mike, Stephen,
> 
> A fixup for a rk3399 clock name as well as the GRF-portions of
> my cleanup series. As Stephen had some mild reservations about the
> introduced indirection in the pll parts and we don't save to much lines
> with my modifications for the currently supported pll-types, I think it's
> easier to postpone those until the next new pll type comes around.
> 
> Maybe it even has some completely different properties to handle where
> the current "simplification" might even be counter-productive :-) .
> 
> So please pull if possible.
> 
> Thanks
> Heiko
> 
> 
> The following changes since commit fd8bc829336a24b770247eb893111bcb8f1ddedb:
> 
>   clk: rockchip: fix the rk3399 cifout clock (2016-04-25 22:54:51 +0200)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.7-rockchip-clk4

Thanks. Pulled.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

      reply	other threads:[~2016-05-09 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 14:22 [GIT PULL] rockchip clock changes for 4.7 part 4 - some more fixes Heiko Stübner
2016-05-09 14:22 ` Heiko Stübner
2016-05-09 23: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=20160509230516.GB3492@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=heiko@sntech.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.