All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, fengguang.wu@intel.com,
	linux-kernel@vger.kernel.org, rostedt@goodmis.org,
	kbuild-all@01.org
Subject: Re: [PATCH] Add hsize argument in write_buf call of pstore_ftrace_call
Date: Tue, 02 Jul 2013 18:54:08 +1000	[thread overview]
Message-ID: <1372755248.3616.5.camel@pasglop> (raw)
In-Reply-To: <20130702053611.11466.71343.stgit@aruna-ThinkPad-T420>

On Tue, 2013-07-02 at 11:06 +0530, Aruna Balakrishnaiah wrote:
> Incorporate the addition of hsize argument in write_buf callback
> of pstore.

Thanks. I've added that to powerpc-next. It should hit Stephen tomorrow.

Cheers,
Ben.

> Signed-off-by: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
> ---
> 
>  fs/pstore/ftrace.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/pstore/ftrace.c b/fs/pstore/ftrace.c
> index 43b1280..76a4eeb 100644
> --- a/fs/pstore/ftrace.c
> +++ b/fs/pstore/ftrace.c
> @@ -44,7 +44,7 @@ static void notrace pstore_ftrace_call(unsigned long ip,
>  	rec.parent_ip = parent_ip;
>  	pstore_ftrace_encode_cpu(&rec, raw_smp_processor_id());
>  	psinfo->write_buf(PSTORE_TYPE_FTRACE, 0, NULL, 0, (void *)&rec,
> -			  sizeof(rec), psinfo);
> +			  0, sizeof(rec), psinfo);
>  
>  	local_irq_restore(flags);
>  }

WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
	fengguang.wu@intel.com, kbuild-all@01.org, rostedt@goodmis.org
Subject: Re: [PATCH] Add hsize argument in write_buf call of pstore_ftrace_call
Date: Tue, 02 Jul 2013 18:54:08 +1000	[thread overview]
Message-ID: <1372755248.3616.5.camel@pasglop> (raw)
In-Reply-To: <20130702053611.11466.71343.stgit@aruna-ThinkPad-T420>

On Tue, 2013-07-02 at 11:06 +0530, Aruna Balakrishnaiah wrote:
> Incorporate the addition of hsize argument in write_buf callback
> of pstore.

Thanks. I've added that to powerpc-next. It should hit Stephen tomorrow.

Cheers,
Ben.

> Signed-off-by: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
> ---
> 
>  fs/pstore/ftrace.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/pstore/ftrace.c b/fs/pstore/ftrace.c
> index 43b1280..76a4eeb 100644
> --- a/fs/pstore/ftrace.c
> +++ b/fs/pstore/ftrace.c
> @@ -44,7 +44,7 @@ static void notrace pstore_ftrace_call(unsigned long ip,
>  	rec.parent_ip = parent_ip;
>  	pstore_ftrace_encode_cpu(&rec, raw_smp_processor_id());
>  	psinfo->write_buf(PSTORE_TYPE_FTRACE, 0, NULL, 0, (void *)&rec,
> -			  sizeof(rec), psinfo);
> +			  0, sizeof(rec), psinfo);
>  
>  	local_irq_restore(flags);
>  }



  reply	other threads:[~2013-07-02  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02  5:36 [PATCH] Add hsize argument in write_buf call of pstore_ftrace_call Aruna Balakrishnaiah
2013-07-02  8:54 ` Benjamin Herrenschmidt [this message]
2013-07-02  8:54   ` Benjamin Herrenschmidt

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=1372755248.3616.5.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=aruna@linux.vnet.ibm.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rostedt@goodmis.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 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.