From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: OpenBMC Patches <openbmc-patches@stwcx.xyz>, openbmc@lists.ozlabs.org
Cc: Norman James <nkskjames@gmail.com>
Subject: Re: [PATCH phosphor-host-ipmid v2] DCMI GET_POWER_LEVEL bad return code
Date: Wed, 09 Mar 2016 16:25:30 +1100 [thread overview]
Message-ID: <87io0w9q9h.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1457453438-9977-2-git-send-email-openbmc-patches@stwcx.xyz>
OpenBMC Patches <openbmc-patches@stwcx.xyz> writes:
> From: Norman James <njames@us.ibm.com>
>
> This function uses static data and should always
> return a good return code. This was causing OCC
> not to start.
>
> Signed-off-by: Norman James <nkskjames@gmail.com>
> ---
> dcmihandler.C | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/dcmihandler.C b/dcmihandler.C
> index fafebdc..5e7d879 100644
> --- a/dcmihandler.C
> +++ b/dcmihandler.C
> @@ -11,7 +11,7 @@ ipmi_ret_t ipmi_dcmi_get_power_limit(ipmi_netfn_t netfn, ipmi_cmd_t cmd,
> ipmi_request_t request, ipmi_response_t response,
> ipmi_data_len_t data_len, ipmi_context_t context)
> {
> - ipmi_ret_t rc = IPMI_DCMI_CC_NO_ACTIVE_POWER_LIMIT;
> + ipmi_ret_t rc = 0;
>
> // dcmi-v1-5-rev-spec.pdf 6.6.2.
Shouldn't the value of rc be something that is an ipmi_ret_t ?
> // This is good enough for OpenBMC support for OpenPOWER based systems
> @@ -37,4 +37,3 @@ void register_netfn_dcmi_functions()
> ipmi_register_callback(NETFUN_GRPEXT, IPMI_CMD_DCMI_GET_POWER, NULL, ipmi_dcmi_get_power_limit);
> return;
> }
> -// 956379
> \ No newline at end of file
Above hunk is irrelevant.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2016-03-09 5:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 16:10 [PATCH phosphor-host-ipmid v2] DCMI GET_POWER_LEVEL bad return code OpenBMC Patches
2016-03-08 16:10 ` OpenBMC Patches
2016-03-08 17:33 ` Chris Austen
2016-03-09 5:25 ` Stewart Smith [this message]
2016-03-09 5:50 ` Norman James
2016-03-09 5:54 ` Vishwanatha Subbanna
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=87io0w9q9h.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=nkskjames@gmail.com \
--cc=openbmc-patches@stwcx.xyz \
--cc=openbmc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.