From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: linux-arm-kernel@lists.infradead.org, mturquette@linaro.org
Cc: devicetree@vger.kernel.org, linux@arm.linux.org.uk,
t.figa@samsung.com, linux-kernel@vger.kernel.org,
b.brezillon@overkiz.com, khilman@linaro.org, festevam@gmail.com,
shawn.guo@linaro.org, kernel@pengutronix.de,
nicolas.ferre@atmel.com, plagnioj@jcrosoft.com
Subject: Re: [PATCH] clk: register fixed-clock only if #clock-cells property is present
Date: Thu, 27 Mar 2014 11:55:47 +0100 [thread overview]
Message-ID: <533403B3.6070602@samsung.com> (raw)
In-Reply-To: <1395858127-18730-1-git-send-email-s.nawrocki@samsung.com>
Mike, please ignore this patch for now. It turns out a less intrusive
change [1] is enough to fix the regressions on both imx and exynos.
I'm going to address the issue properly for next kernel release and
make exynos use regular fixed-clock driver, rather than registering
the external clock generators within the SoC main clock controller
driver.
--
Thanks,
Sylwester
[1] http://permalink.gmane.org/gmane.linux.kernel/1673639
prev parent reply other threads:[~2014-03-27 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 18:22 [PATCH] clk: register fixed-clock only if #clock-cells property is present Sylwester Nawrocki
2014-03-26 18:33 ` Fabio Estevam
2014-03-26 19:57 ` Sylwester Nawrocki
2014-03-26 20:14 ` Fabio Estevam
2014-03-26 20:25 ` Gregory CLEMENT
2014-03-26 20:34 ` Fabio Estevam
2014-03-27 7:58 ` Boris BREZILLON
2014-03-27 8:11 ` [PATCH] ARM: imx6/dt: add ccm dependency upon ckil, ckih1 and osc clocks Boris BREZILLON
2014-03-27 8:39 ` Boris BREZILLON
2014-03-27 11:19 ` Fabio Estevam
2014-03-27 13:27 ` Boris BREZILLON
2014-03-27 10:01 ` [PATCH] clk: register fixed-clock only if #clock-cells property is present Sylwester Nawrocki
2014-03-27 11:14 ` Boris BREZILLON
2014-03-27 10:55 ` Sylwester Nawrocki [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=533403B3.6070602@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=b.brezillon@overkiz.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=shawn.guo@linaro.org \
--cc=t.figa@samsung.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;
as well as URLs for NNTP newsgroup(s).