Thread (2 messages) 2 messages, 2 authors, 2018-12-23

Re: powerpc/powernv: Move opal_power_control_init() call in opal_init().

From: Michael Ellerman <hidden>
Date: 2018-12-23 13:54:08

On Thu, 2018-12-13 at 05:47:31 UTC, Mahesh J Salgaonkar wrote:
From: Mahesh Salgaonkar <redacted>

opal_power_control_init() depends on opal message notifier to be
initialized, which is done in opal_init()->opal_message_init(). But both
these initialization are called through machine initcalls and it all
depends on in which order they being called. So far these are called in
correct order (may be we got lucky) and never saw any issue. But it is
clearer to control initialization order explicitly by moving
opal_power_control_init() into opal_init().

Signed-off-by: Mahesh Salgaonkar <redacted>
Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/08fb726df13778a54592aaa1deea6a

cheers
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help