From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: ananth@in.ibm.com
Cc: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
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 15:32:30 +1000 [thread overview]
Message-ID: <1366695150.2886.14.camel@pasglop> (raw)
In-Reply-To: <20130423050540.GA30690@in.ibm.com>
On Tue, 2013-04-23 at 10:35 +0530, Ananth N Mavinakayanahalli wrote:
> On Tue, Apr 23, 2013 at 10:40:10AM +1000, Benjamin Herrenschmidt wrote:
> > 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,
>
> The userspace update_flash script invokes the rtas_flash module. With
> upcoming System p servers, the firmware will have the entitlement dates
> encoded in it and RTAS will return an error if the entitlement has
> expired. All we need from this module is for it to return that new error
> which will then be communicated to the user by the update_flash.
That doesn't answer my question :-)
What is the point of adding a #define to a piece of code without any user
of that definition and in a file that isn't exposed to user space ?
IE. What is the point of the patch ?
Cheers,
Ben.
next prev parent reply other threads:[~2013-04-23 5:32 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
2013-04-23 5:05 ` Ananth N Mavinakayanahalli
2013-04-23 5:32 ` Benjamin Herrenschmidt [this message]
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=1366695150.2886.14.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ananth@in.ibm.com \
--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).