The display timing node was added:
7ed2077 ARM: dts: Add display timing node to exynos5250-smdk5250.dts
...and looks OK there. ...but it looks like we lost a }; in the
merge and it no longer compiles. Fix it.
Signed-off-by: Doug Anderson diand...@chromium.org
---
On 04/09/13 01:51, Doug Anderson wrote:
The display timing node was added:
7ed2077 ARM: dts: Add display timing node to exynos5250-smdk5250.dts
...and looks OK there. ...but it looks like we lost a }; in the
merge and it no longer compiles. Fix it.
Signed-off-by: Doug
Kukjin,
On Mon, Apr 8, 2013 at 11:23 AM, Kukjin Kim kgene@samsung.com wrote:
Thanks for your pointing out. But it should be fixed with re-sorting out the
branch.
No problem with however you want to solve it. ;) Seemed that the
patch was the easiest way to report the problem in any
On 04/09/13 03:25, Doug Anderson wrote:
Kukjin,
On Mon, Apr 8, 2013 at 11:23 AM, Kukjin Kimkgene@samsung.com wrote:
Thanks for your pointing out. But it should be fixed with re-sorting out the
branch.
No problem with however you want to solve it. ;) Seemed that the
patch was the
Kukjin,
On Mon, Apr 8, 2013 at 11:29 AM, Kukjin Kim kgene@gmail.com wrote:
BTW, if any problems on current for-next, please kindly let me know.
I usually try to check linux-next at least once a week, but sometimes
it's more or less often. At the moment I'm trying to track something
weird
Hi Doug,
On Monday 08 of April 2013 12:21:32 Doug Anderson wrote:
Kukjin,
On Mon, Apr 8, 2013 at 11:29 AM, Kukjin Kim kgene@gmail.com wrote:
BTW, if any problems on current for-next, please kindly let me know.
I usually try to check linux-next at least once a week, but sometimes
Tomasz,
On Mon, Apr 8, 2013 at 12:27 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
Common Clock Framework by default automatically gates unused clocks, just
like regulator core does with unused regulators. Maybe this is the cause?
Yes, I'm nearly certain that's the case here. The reset code
