From: Heiko Stuebner <heiko@sntech.de>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: zhengxing@rock-chips.com, xf@rock-chips.com,
linux-arm-kernel@lists.infradead.org, huangtao@rock-chips.com,
zyw@rock-chips.com, xxx@rock-chips.com, jay.xu@rock-chips.com,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] clk: rockchip: include downstream muxes into fractional dividers on rk3368
Date: Fri, 26 Feb 2016 02:13:48 +0100 [thread overview]
Message-ID: <4704515.DI1k3PeUbF@phil> (raw)
In-Reply-To: <1456274651-23202-1-git-send-email-zhangqing@rock-chips.com>
Am Mittwoch, 24. Februar 2016, 08:44:11 schrieb Elaine Zhang:
> During the initial conversion to the newly introduced combined fractional
> dividers+muxes the rk3368 clocks were left out, so convert them now.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
applied to my clk-branch
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] clk: rockchip: include downstream muxes into fractional dividers on rk3368
Date: Fri, 26 Feb 2016 02:13:48 +0100 [thread overview]
Message-ID: <4704515.DI1k3PeUbF@phil> (raw)
In-Reply-To: <1456274651-23202-1-git-send-email-zhangqing@rock-chips.com>
Am Mittwoch, 24. Februar 2016, 08:44:11 schrieb Elaine Zhang:
> During the initial conversion to the newly introduced combined fractional
> dividers+muxes the rk3368 clocks were left out, so convert them now.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
applied to my clk-branch
Thanks
Heiko
next prev parent reply other threads:[~2016-02-26 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 0:44 [RESEND PATCH] clk: rockchip: include downstream muxes into fractional dividers on rk3368 Elaine Zhang
2016-02-24 0:44 ` Elaine Zhang
2016-02-26 1:13 ` Heiko Stuebner [this message]
2016-02-26 1:13 ` Heiko Stuebner
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=4704515.DI1k3PeUbF@phil \
--to=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=xf@rock-chips.com \
--cc=xxx@rock-chips.com \
--cc=zhangqing@rock-chips.com \
--cc=zhengxing@rock-chips.com \
--cc=zyw@rock-chips.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.