From: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
To: Joel Stanley <joel@jms.id.au>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/powernv: Silence SYSPARAM warning on boot
Date: Fri, 01 May 2015 22:02:07 +0530 [thread overview]
Message-ID: <5543AA87.9020009@linux.vnet.ibm.com> (raw)
In-Reply-To: <1430365807-14493-1-git-send-email-joel@jms.id.au>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On 04/30/2015 09:20 AM, Joel Stanley wrote:
> OpenPower BMC machines do not place any sysparams in the device tree, so
> at every boot we get a warning:
>
> [ 0.437176] SYSPARAM: Opal sysparam node not found
>
> Remove the warning, and reorder the init so we don't peform allocations
> when there is no sysparam node in the device tree.
Acked-by: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> arch/powerpc/platforms/powernv/opal-sysparam.c | 31 +++++++++++++-------------
> 1 file changed, 15 insertions(+), 16 deletions(-)
>
>
[-- Attachment #2: Type: text/html, Size: 1284 bytes --]
prev parent reply other threads:[~2015-05-01 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 3:50 [PATCH] powerpc/powernv: Silence SYSPARAM warning on boot Joel Stanley
2015-05-01 16:32 ` Neelesh Gupta [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=5543AA87.9020009@linux.vnet.ibm.com \
--to=neelegup@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@ozlabs.org \
/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).