From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Stewart Smith <stewart@linux.vnet.ibm.com>,
Vipin K Parasher <vipin@linux.vnet.ibm.com>
Subject: Re: powerpc/powernv: Move opal_power_control_init() call in opal_init().
Date: Mon, 24 Dec 2018 00:28:02 +1100 (AEDT) [thread overview]
Message-ID: <43N38L57Zdz9sMp@ozlabs.org> (raw)
In-Reply-To: <154468000191.27281.9764771421364806592.stgit@jupiter.in.ibm.com>
On Thu, 2018-12-13 at 05:47:31 UTC, Mahesh J Salgaonkar wrote:
> From: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
>
> 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 <mahesh@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/08fb726df13778a54592aaa1deea6a
cheers
prev parent reply other threads:[~2018-12-23 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 5:47 [PATCH] powerpc/powernv: Move opal_power_control_init() call in opal_init() Mahesh J Salgaonkar
2018-12-23 13:28 ` Michael Ellerman [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=43N38L57Zdz9sMp@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=stewart@linux.vnet.ibm.com \
--cc=vipin@linux.vnet.ibm.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).