From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
Tony Luck <tony.luck@intel.com>,
Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>
Subject: Re: [PATCH v5 2/4] pstore: Add pstore type id for PPC64 opal nvram partition
Date: Wed, 04 Mar 2015 11:42:40 +0530 [thread overview]
Message-ID: <54F6A258.2080402@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150205193628.24669.79936.stgit@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
On 02/06/2015 01:06 AM, Hari Bathini wrote:
> This patch adds a new PPC64 partition type to be used for opal
> specific nvram partition. A new partition type is needed as none
> of the existing type matches this partition type.
>
> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
This patch series is reviewed by Kees.
Reference link: https://lkml.org/lkml/2015/2/5/651
Reviewed-by: Kees Cook <keescook@chromium.org>
Thanks
Hari
> ---
> fs/pstore/inode.c | 3 +++
> include/linux/pstore.h | 1 +
> 2 files changed, 4 insertions(+)
>
> diff --git a/fs/pstore/inode.c b/fs/pstore/inode.c
> index 5041660..8e0c009 100644
> --- a/fs/pstore/inode.c
> +++ b/fs/pstore/inode.c
> @@ -359,6 +359,9 @@ int pstore_mkfile(enum pstore_type_id type, char *psname, u64 id, int count,
> case PSTORE_TYPE_PPC_COMMON:
> sprintf(name, "powerpc-common-%s-%lld", psname, id);
> break;
> + case PSTORE_TYPE_PPC_OPAL:
> + sprintf(name, "powerpc-opal-%s-%lld", psname, id);
> + break;
> case PSTORE_TYPE_UNKNOWN:
> sprintf(name, "unknown-%s-%lld", psname, id);
> break;
> diff --git a/include/linux/pstore.h b/include/linux/pstore.h
> index ece0c6b..af44980 100644
> --- a/include/linux/pstore.h
> +++ b/include/linux/pstore.h
> @@ -39,6 +39,7 @@ enum pstore_type_id {
> PSTORE_TYPE_PPC_RTAS = 4,
> PSTORE_TYPE_PPC_OF = 5,
> PSTORE_TYPE_PPC_COMMON = 6,
> + PSTORE_TYPE_PPC_OPAL = 7,
> PSTORE_TYPE_UNKNOWN = 255
> };
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
[-- Attachment #2: Type: text/html, Size: 2607 bytes --]
next prev parent reply other threads:[~2015-03-04 6:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 19:35 [PATCH v5 0/4] powerpc/pstore: Add pstore support for nvram partitions Hari Bathini
2015-02-05 19:35 ` Hari Bathini
2015-02-05 19:36 ` [PATCH v5 1/4] powerpc/nvram: move generic code for nvram and pstore Hari Bathini
2015-02-05 19:36 ` Hari Bathini
2015-03-23 3:11 ` [v5,1/4] " Michael Ellerman
2015-02-05 19:36 ` [PATCH v5 2/4] pstore: Add pstore type id for PPC64 opal nvram partition Hari Bathini
2015-02-05 19:36 ` Hari Bathini
2015-03-04 6:12 ` Hari Bathini [this message]
2015-02-05 19:36 ` [PATCH v5 3/4] pstore: add pstore support on powernv Hari Bathini
2015-02-05 19:36 ` Hari Bathini
2015-02-05 19:37 ` [PATCH v5 4/4] powerpc: make timestamp related code y2038-safe Hari Bathini
2015-02-05 19:37 ` Hari Bathini
2015-02-05 21:28 ` [PATCH v5 0/4] powerpc/pstore: Add pstore support for nvram partitions Kees Cook
2015-02-05 21:28 ` Kees Cook
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=54F6A258.2080402@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=tony.luck@intel.com \
/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.