Re: [PATCH] i2c: pnx: fix warnings caused by enabling unprepared clock

On Sat, Oct 17, 2015 at 09:52:27PM +0300, Vladimir Zapolskiy wrote: > If common clock framework is configured, the driver generates a warning, > which is fixed by this change: > > WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:727 > clk_core_enable+0x2c/0xa4() > Modules linked in: >

Re: [PATCH] i2c: pnx: fix warnings caused by enabling unprepared clock

> Applied to for-next with your updated commit message, thanks! Actually, applied to for-current, thanks! signature.asc Description: Digital signature

Re: [PATCH] i2c: pnx: fix warnings caused by enabling unprepared clock

On Mon, Oct 19, 2015 at 11:49 PM, Vladimir Zapolskiy wrote: > On 19.10.2015 19:21, Shubhrajyoti Datta wrote: >> On Sun, Oct 18, 2015 at 12:22 AM, Vladimir Zapolskiy wrote: >>> If common clock framework is configured, the driver generates a warning, >>> which is

Re: [PATCH] i2c: pnx: fix warnings caused by enabling unprepared clock

On 19.10.2015 19:21, Shubhrajyoti Datta wrote: > On Sun, Oct 18, 2015 at 12:22 AM, Vladimir Zapolskiy wrote: >> If common clock framework is configured, the driver generates a warning, >> which is fixed by this change: > Maybe just describe the issue and the fix. > Is it just a

Re: [PATCH] i2c: pnx: fix warnings caused by enabling unprepared clock

On Sun, Oct 18, 2015 at 12:22 AM, Vladimir Zapolskiy wrote: > If common clock framework is configured, the driver generates a warning, > which is fixed by this change: Maybe just describe the issue and the fix. Is it just a warning or the clk enable doesn't work ? I feel the

[PATCH] i2c: pnx: fix warnings caused by enabling unprepared clock

If common clock framework is configured, the driver generates a warning, which is fixed by this change: WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:727 clk_core_enable+0x2c/0xa4() Modules linked in: CPU: 0 PID: 1 Comm: swapper Not tainted 4.3.0-rc2+ #171 Hardware name: LPC32XX SoC