All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [2/2] pstore: add pstore support on powernv
Date: Fri, 05 Dec 2014 10:45:10 +0530	[thread overview]
Message-ID: <54813F5E.601@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141204053708.E24341400EA@ozlabs.org>

On 12/04/2014 11:07 AM, Michael Ellerman wrote:
> On Wed, 2014-03-12 at 11:03:15 UTC, Hari Bathini wrote:
>> This patch extends pstore, a generic interface to platform dependent
>> persistent storage, support for powernv  platform to capture certain
>> useful information, during dying moments. Such support is already in
>> place for  pseries platform.  This patch while adding pstore support
>> for  powernv platform,  moves common code for pseries and powernv to
>> arch/powerpc/kernel/nvram_64.c file.
> Please move the common code first in a separate patch. Unless there's some
> reason you absolutely can't do that.

Sure, Michael. Let me make the changes as suggested and
post the updated patch series.

Thanks
Hari

> cheers
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

      reply	other threads:[~2014-12-05  5:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 11:02 [PATCH 0/2] powerpc/pstore: Add pstore support for nvram partitions Hari Bathini
2014-12-03 11:02 ` [PATCH 1/2] pstore: Add pstore type id for firmware partition Hari Bathini
2014-12-03 11:03 ` [PATCH 2/2] pstore: add pstore support on powernv Hari Bathini
2014-12-04  5:37   ` [2/2] " Michael Ellerman
2014-12-05  5:15     ` Hari Bathini [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=54813F5E.601@linux.vnet.ibm.com \
    --to=hbathini@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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.