public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: David VomLehn <dvomlehn@cisco.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-arch@vger.kernel.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/23] Make register values available to Alpha panic	notifiers
Date: Wed, 14 Apr 2010 17:10:58 -0400	[thread overview]
Message-ID: <4BC62F62.40500@cisco.com> (raw)
In-Reply-To: <20100412190509.GA17147@merkur.ravnborg.org>

Sam Ravnborg wrote:
> On Sun, Apr 11, 2010 at 11:06:13PM -0700, David VomLehn wrote:
>   
>> The save_ptregs() function has not been tested or even built. I will need
>> help to complete this.
>>
>> Signed-off-by: David VomLehn <dvomlehn@cisco.com>
>> ---
>>  arch/alpha/include/asm/ptrace.h |  124 +++++++++++++++++++++++++++++++++++++++
>>  1 files changed, 124 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/alpha/include/asm/ptrace.h b/arch/alpha/include/asm/ptrace.h
>> index 65cf3e2..952d177 100644
>> --- a/arch/alpha/include/asm/ptrace.h
>> +++ b/arch/alpha/include/asm/ptrace.h
>> @@ -79,6 +79,130 @@ extern void show_regs(struct pt_regs *);
>>  
>>  #define force_successful_syscall_return() (task_pt_regs(current)->r0 = 0)
>>  
>> +/* Macros for saving the contents of registers and for the output constraint
>> + * for those registers */
>> +#include "/home/vomlehn/git/kernel.org/linux/ptreg.h"
>>     
> The above include needs fixing.
>
> 	Sam
>   
Definitely, thanks!

  reply	other threads:[~2010-04-14 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12  6:06 [PATCH 2/23] Make register values available to Alpha panic notifiers David VomLehn
2010-04-12 19:06 ` Sam Ravnborg
2010-04-14 21:10   ` David VomLehn [this message]
2010-04-14 21:10     ` David VomLehn

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=4BC62F62.40500@cisco.com \
    --to=dvomlehn@cisco.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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