From: Haojian Zhuang <haojian.zhuang@linaro.org>
To: Mike Turquette <mturquette@linaro.org>,
zhangfei <zhangfei.gao@linaro.org>, Chris Ball <cjb@laptop.org>,
Arnd Bergmann <arnd@arndb.de>,
Jaehoon Chung <jh80.chung@samsung.com>,
Seungwon Jeon <tgih.jun@samsung.com>,
brooke.wangzhigang@huawei.com
Cc: linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
patches@linaro.org, devicetree@vger.kernel.org,
Kevin Hilman <khilman@linaro.org>
Subject: Re: [PATCH 1/2] clk: hisilicon: add hi3620_mmc_clks
Date: Wed, 15 Jan 2014 13:59:40 +0800 [thread overview]
Message-ID: <52D623CC.50009@linaro.org> (raw)
In-Reply-To: <20140115035339.4167.51194@quantum>
On 01/15/2014 11:53 AM, Mike Turquette wrote:
> Quoting zhangfei (2014-01-14 17:40:25)
>> Dear Mike
>>
>> On 01/15/2014 04:17 AM, Mike Turquette wrote:
>>> Quoting Zhangfei Gao (2014-01-13 01:14:28)
>>>> Suggest by Arnd: abstract mmc tuning as clock behavior,
>>>> also because different soc have different tuning method and registers.
>>>> hi3620_mmc_clks is added to handle mmc clock specifically on hi3620.
>>>>
>>>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>>>> Acked-by: Arnd Bergmann <arnd@arndb.de>
>>>> Acked-by: Jaehoon Chung <jh80.chung@samsung.com>
>>> Patch looks good to me with one exception. I do not have
>>> Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt in the
>>> clk-next branch. Is there a stable branch I can pull in as a dependency?
>> Mach-hisi just have been uploaeded.
>> Have tried next-20140114, the patch can be applied successfully.
>> While v3.13-rc8 still can not.
>>
>> Is this fine?
> Can you give me a link to the branch that introduces
> Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt?
>
> I guess the patch introducing it is going through arm-soc. Is this going
> in for 3.14? If so then perhaps the clk tree and the arm-soc tree can
> share a stable branch that introduces it.
>
> Regards,
> Mike
>
Some patches are merged into arm-soc, and others are in clk tree.
If sharing a stable branch between arm-soc and clk tree, it only means
that we need to revert all commits that are in arm-soc and clk tree.
I think it's too complex.
How about split the patch? The patch on document should enter in arm-soc.
Regards
Haojian
WARNING: multiple messages have this Message-ID (diff)
From: haojian.zhuang@linaro.org (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: hisilicon: add hi3620_mmc_clks
Date: Wed, 15 Jan 2014 13:59:40 +0800 [thread overview]
Message-ID: <52D623CC.50009@linaro.org> (raw)
In-Reply-To: <20140115035339.4167.51194@quantum>
On 01/15/2014 11:53 AM, Mike Turquette wrote:
> Quoting zhangfei (2014-01-14 17:40:25)
>> Dear Mike
>>
>> On 01/15/2014 04:17 AM, Mike Turquette wrote:
>>> Quoting Zhangfei Gao (2014-01-13 01:14:28)
>>>> Suggest by Arnd: abstract mmc tuning as clock behavior,
>>>> also because different soc have different tuning method and registers.
>>>> hi3620_mmc_clks is added to handle mmc clock specifically on hi3620.
>>>>
>>>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>>>> Acked-by: Arnd Bergmann <arnd@arndb.de>
>>>> Acked-by: Jaehoon Chung <jh80.chung@samsung.com>
>>> Patch looks good to me with one exception. I do not have
>>> Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt in the
>>> clk-next branch. Is there a stable branch I can pull in as a dependency?
>> Mach-hisi just have been uploaeded.
>> Have tried next-20140114, the patch can be applied successfully.
>> While v3.13-rc8 still can not.
>>
>> Is this fine?
> Can you give me a link to the branch that introduces
> Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt?
>
> I guess the patch introducing it is going through arm-soc. Is this going
> in for 3.14? If so then perhaps the clk tree and the arm-soc tree can
> share a stable branch that introduces it.
>
> Regards,
> Mike
>
Some patches are merged into arm-soc, and others are in clk tree.
If sharing a stable branch between arm-soc and clk tree, it only means
that we need to revert all commits that are in arm-soc and clk tree.
I think it's too complex.
How about split the patch? The patch on document should enter in arm-soc.
Regards
Haojian
next prev parent reply other threads:[~2014-01-15 5:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 9:14 [PATCH 0/2] mmc: dw_mmc: k3 remove clk_table Zhangfei Gao
2014-01-13 9:14 ` Zhangfei Gao
2014-01-13 9:14 ` [PATCH 1/2] clk: hisilicon: add hi3620_mmc_clks Zhangfei Gao
2014-01-13 9:14 ` Zhangfei Gao
2014-01-13 9:37 ` [PATCH] " Zhangfei Gao
2014-01-13 9:37 ` Zhangfei Gao
2014-02-27 0:10 ` Mike Turquette
2014-02-27 0:10 ` Mike Turquette
2014-01-14 9:47 ` [PATCH 1/2] " Seungwon Jeon
2014-01-14 9:47 ` Seungwon Jeon
2014-01-14 10:04 ` Zhangfei Gao
2014-01-14 10:04 ` Zhangfei Gao
2014-01-14 10:40 ` Seungwon Jeon
2014-01-14 10:40 ` Seungwon Jeon
2014-01-14 11:52 ` zhangfei
2014-01-14 11:52 ` zhangfei
[not found] ` <1389604469-8064-2-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-01-14 20:17 ` Mike Turquette
2014-01-14 20:17 ` Mike Turquette
2014-01-15 1:40 ` zhangfei
2014-01-15 1:40 ` zhangfei
2014-01-15 3:53 ` Mike Turquette
2014-01-15 3:53 ` Mike Turquette
2014-01-15 5:59 ` Haojian Zhuang [this message]
2014-01-15 5:59 ` Haojian Zhuang
2014-01-15 8:29 ` Mike Turquette
2014-01-15 8:29 ` Mike Turquette
2014-01-15 9:34 ` Haojian Zhuang
2014-01-15 9:34 ` Haojian Zhuang
2014-01-15 16:14 ` Kevin Hilman
2014-01-15 16:14 ` Kevin Hilman
2014-01-13 9:14 ` [PATCH 2/2] mmc: dw_mmc: k3: remove clk_table Zhangfei Gao
2014-01-13 9:14 ` Zhangfei Gao
2014-01-14 10:42 ` Seungwon Jeon
2014-01-14 10:42 ` Seungwon Jeon
[not found] ` <002b01cf1115$4cdfe240$e69fa6c0$%jun-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-01-17 15:01 ` Chris Ball
2014-01-17 15:01 ` Chris Ball
2014-01-17 16:10 ` Seungwon Jeon
2014-01-17 16:10 ` Seungwon Jeon
2014-01-17 22:56 ` Mike Turquette
2014-01-17 22:56 ` Mike Turquette
2014-01-17 23:00 ` Chris Ball
2014-01-17 23:00 ` Chris Ball
2014-01-17 14:43 ` Seungwon Jeon
2014-01-17 14:43 ` Seungwon Jeon
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=52D623CC.50009@linaro.org \
--to=haojian.zhuang@linaro.org \
--cc=arnd@arndb.de \
--cc=brooke.wangzhigang@huawei.com \
--cc=cjb@laptop.org \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=patches@linaro.org \
--cc=tgih.jun@samsung.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.