From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/rtas_flash: New return code to indicate FW entitlement expiry
Date: Tue, 23 Apr 2013 10:40:10 +1000 [thread overview]
Message-ID: <1366677610.2886.8.camel@pasglop> (raw)
In-Reply-To: <20130419114410.19115.35846.stgit@hegdevasant>
On Fri, 2013-04-19 at 17:14 +0530, Vasant Hegde wrote:
> Add new return code to rtas_flash to indicate firmware entitlement
> expiry. This will be used by the update_flash script to return
> appropriate message to the user.
What's the point of that patch ? It adds a definition to a private .c
file not exposed to user space and doesn't do anything with it ...
Ben.
> Signed-off-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
> Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
> ---
> arch/powerpc/kernel/rtas_flash.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/powerpc/kernel/rtas_flash.c b/arch/powerpc/kernel/rtas_flash.c
> index a7020d2..0a12c16 100644
> --- a/arch/powerpc/kernel/rtas_flash.c
> +++ b/arch/powerpc/kernel/rtas_flash.c
> @@ -64,6 +64,7 @@
> #define VALIDATE_TMP_COMMIT_DL 4 /* Validate Return Status */
> #define VALIDATE_TMP_COMMIT 5 /* Validate Return Status */
> #define VALIDATE_TMP_UPDATE_DL 6 /* Validate Return Status */
> +#define VALIDATE_OUT_OF_WRNTY 7 /* Validate Return Status */
>
> /* ibm,manage-flash-image operation tokens */
> #define RTAS_REJECT_TMP_IMG 0
next prev parent reply other threads:[~2013-04-23 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 11:44 [PATCH] powerpc/rtas_flash: New return code to indicate FW entitlement expiry Vasant Hegde
2013-04-23 0:40 ` Benjamin Herrenschmidt [this message]
2013-04-23 5:05 ` Ananth N Mavinakayanahalli
2013-04-23 5:32 ` Benjamin Herrenschmidt
2013-04-23 5:47 ` Ananth N Mavinakayanahalli
2013-04-23 5:29 ` Vasant Hegde
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=1366677610.2886.8.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).