From: Stephen Boyd <sboyd@codeaurora.org>
To: Jiancheng Xue <xuejiancheng@hisilicon.com>
Cc: mturquette@baylibre.com, p.zabel@pengutronix.de,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
yanhaifeng@hisilicon.com, haojian.zhuang@linaro.org,
zhangfei.gao@linaro.org, xuwei5@hisilicon.com,
yanghongwei@hisilicon.com
Subject: Re: [PATCH 0/5] clk: hisilicon: Fix some problems of clk-hi3519
Date: Thu, 12 May 2016 17:09:06 -0700 [thread overview]
Message-ID: <20160513000900.GP3492@codeaurora.org> (raw)
In-Reply-To: <1462871953-26606-1-git-send-email-xuejiancheng@hisilicon.com>
On 05/10, Jiancheng Xue wrote:
> This patch is base on branch clk-hi3519 in clk tree. It mainly fixes the
> following issues:
> 1. Add driver remove path.
> 2. Fix the ordering issue about clock provider being published.
> 3. Add error checking upon registering clocks.
I'm waiting for round 2. Otherwise it looks ok.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-05-13 0:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 9:19 [PATCH 0/5] clk: hisilicon: Fix some problems of clk-hi3519 Jiancheng Xue
2016-05-10 9:19 ` [PATCH 1/5] reset: hisilicon: change the definition of hisi_reset_init Jiancheng Xue
2016-05-10 11:09 ` Philipp Zabel
2016-05-10 9:19 ` [PATCH 2/5] clk: hisilicon: add hisi_clk_alloc function Jiancheng Xue
2016-05-10 9:19 ` [PATCH 3/5] clk: hisilicon: add error processing for hisi_clk_register_* functions Jiancheng Xue
2016-05-10 9:19 ` [PATCH 4/5] clk: hisilicon: add hisi_clk_unregister_* functions Jiancheng Xue
2016-05-10 9:19 ` [PATCH 5/5] clk: hisilicon: hi3519: add driver remove path and fix some issues Jiancheng Xue
2016-05-10 11:09 ` Philipp Zabel
2016-05-10 11:46 ` Jiancheng Xue
2016-05-13 0:09 ` 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=20160513000900.GP3492@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=haojian.zhuang@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=xuejiancheng@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=yanghongwei@hisilicon.com \
--cc=yanhaifeng@hisilicon.com \
--cc=zhangfei.gao@linaro.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 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.