From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 3/5] powerpc: Reduce log level of "OPAL detected !" message
Date: Tue, 16 Jan 2018 11:59:49 +1100 [thread overview]
Message-ID: <87r2qq39fe.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180112022849.30899-3-benh@kernel.crashing.org>
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> This message isn't terribly useful.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: Stewart Smith <stewart@linux.vnet.ibm.com>
> --- a/arch/powerpc/platforms/powernv/opal.c
> +++ b/arch/powerpc/platforms/powernv/opal.c
> @@ -127,7 +127,7 @@ int __init early_init_dt_scan_opal(unsigned long node,
>
> if (of_flat_dt_is_compatible(node, "ibm,opal-v3")) {
> powerpc_firmware_features |= FW_FEATURE_OPAL;
> - pr_info("OPAL detected !\n");
> + pr_debug("OPAL detected !\n");
I've been meaning to add in a thing to grab the version from the device
tree and print that too.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-01-16 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 2:28 [PATCH 1/5] powerpc/xive: Remove incorrect debug code Benjamin Herrenschmidt
2018-01-12 2:28 ` [PATCH 2/5] powerpc: Remove DEBUG define in 64-bit early setup code Benjamin Herrenschmidt
2018-01-12 2:28 ` [PATCH 3/5] powerpc: Reduce log level of "OPAL detected !" message Benjamin Herrenschmidt
2018-01-16 0:59 ` Stewart Smith [this message]
2018-01-12 2:28 ` [PATCH 4/5] powerpc: Remove useless EXC_COMMON_HV Benjamin Herrenschmidt
2018-01-17 13:30 ` [4/5] " Michael Ellerman
2018-01-12 2:28 ` [PATCH 5/5] powerpc: Use the TRAP macro whenever comparing a trap number Benjamin Herrenschmidt
2018-01-17 13:30 ` [5/5] " Michael Ellerman
2018-01-17 13:30 ` [1/5] powerpc/xive: Remove incorrect debug code Michael Ellerman
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=87r2qq39fe.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.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).