From: Heiko Stuebner <heiko@sntech.de>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Xing Zheng <zhengxing@rock-chips.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] clk: rockchip: remove mux_core_reg from rockchip_cpuclk_reg_data
Date: Mon, 14 Mar 2016 01:13:10 +0100 [thread overview]
Message-ID: <8493494.xJRFTlmVnL@phil> (raw)
In-Reply-To: <1457799900-3056-1-git-send-email-shawn.lin@rock-chips.com>
Am Sonntag, 13. März 2016, 00:25:00 schrieb Shawn Lin:
> mux_core_reg isn't been used anywhere, let's remove it.
>
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
applied for v4.7
Thanks
Heiko
next prev parent reply other threads:[~2016-03-14 0:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 16:24 [PATCH 0/7] Some trivial patches for rockchip clk stuff Shawn Lin
2016-03-12 16:25 ` [PATCH 1/7] clk: rockchip: remove mux_core_reg from rockchip_cpuclk_reg_data Shawn Lin
2016-03-14 0:13 ` Heiko Stuebner [this message]
2016-03-12 16:25 ` [PATCH 2/7] clk: rockchip: fix warning reported by kernel-doc Shawn Lin
2016-03-14 0:25 ` Heiko Stuebner
2016-03-12 16:25 ` [PATCH 3/7] clk: rockchip: release io resource when rk3036_clk_init failed Shawn Lin
2016-03-12 16:48 ` Heiko Stübner
2016-03-13 1:49 ` Shawn Lin
2016-03-12 16:25 ` [PATCH 4/7] clk: rockchip: release io resource when rk3188_common_clk_init failed Shawn Lin
2016-03-12 16:25 ` [PATCH 5/7] clk: rockchip: release io resource when rk3368_clk_init failed Shawn Lin
2016-03-12 16:25 ` [PATCH 6/7] clk: rockchip: remove redundant checking of device_node Shawn Lin
2016-03-14 0:26 ` Heiko Stuebner
2016-03-12 16:26 ` [PATCH 7/7] clk: rockchip: fix a typo for rockchip_rk3399_pll_set_params Shawn Lin
2016-03-12 16:45 ` Heiko Stübner
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=8493494.xJRFTlmVnL@phil \
--to=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=shawn.lin@rock-chips.com \
--cc=zhengxing@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox