LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: Tony Luck <tony.luck@intel.com>,
	Anton Vorontsov <anton@enomsg.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Colin Cross <ccross@android.com>,
	Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH v5 0/4] powerpc/pstore: Add pstore support for nvram partitions
Date: Thu, 5 Feb 2015 13:28:22 -0800	[thread overview]
Message-ID: <CAGXu5jK-dRTBDkF_cfVuuQRXH80r2-TVTgPZ1fDqYoVMABfaHw@mail.gmail.com> (raw)
In-Reply-To: <20150205193412.24669.8648.stgit@localhost.localdomain>

On Thu, Feb 5, 2015 at 11:35 AM, Hari Bathini
<hbathini@linux.vnet.ibm.com> wrote:
> This patch series adds pstore support on powernv platform to
> read different nvram partitions and write compressed data to
> oops-log nvram partition. As pseries platform already has
> pstore support, this series moves most of the common code
> for pseries and powernv platforms to a common file. Tested
> the patches successfully on both pseries and powernv
> platforms. Also, tested the patches successfully, on a kernel
> compiled with both CONFIG_PPC_PSERIES=y & CONFIG_PPC_POWERNV=y.
>
> Changes from v4:
> 1. Added a patch for y2038-safe code changes
>
> ---
>
> Hari Bathini (4):
>       powerpc/nvram: move generic code for nvram and pstore
>       pstore: Add pstore type id for PPC64 opal nvram partition
>       pstore: add pstore support on powernv
>       powerpc: make timestamp related code y2038-safe

Thanks! I skimmed this, and it looks good to me.

Reviewed-by: Kees Cook <keescook@chromium.org>

-Kees

>
>
>  arch/powerpc/include/asm/nvram.h            |   50 ++
>  arch/powerpc/include/asm/rtas.h             |    5
>  arch/powerpc/kernel/nvram_64.c              |  677 +++++++++++++++++++++++++++
>  arch/powerpc/platforms/powernv/opal-nvram.c |   10
>  arch/powerpc/platforms/pseries/nvram.c      |  673 ---------------------------
>  fs/pstore/inode.c                           |    3
>  include/linux/pstore.h                      |    1
>  7 files changed, 754 insertions(+), 665 deletions(-)
>
> --
> -Hari
>



-- 
Kees Cook
Chrome OS Security

      parent reply	other threads:[~2015-02-05 21:28 UTC|newest]

Thread overview: 7+ 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:36 ` [PATCH v5 1/4] powerpc/nvram: move generic code for nvram and pstore 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 ` [PATCH v5 3/4] pstore: add pstore support on powernv Hari Bathini
2015-02-05 19:37 ` [PATCH v5 4/4] powerpc: make timestamp related code y2038-safe Hari Bathini
2015-02-05 21:28 ` Kees Cook [this message]

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=CAGXu5jK-dRTBDkF_cfVuuQRXH80r2-TVTgPZ1fDqYoVMABfaHw@mail.gmail.com \
    --to=keescook@chromium.org \
    --cc=anton@enomsg.org \
    --cc=benh@kernel.crashing.org \
    --cc=ccross@android.com \
    --cc=hbathini@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    --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 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).