From: Peter Griffin <pgriffin@mpc-data.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] Add ptrace support for NOMMU debugging
Date: Tue, 12 May 2009 08:38:51 +0000 [thread overview]
Message-ID: <1242117531.32597.17.camel@quercus-bis> (raw)
In-Reply-To: <1241794254.16311.32.camel@quercus-bis>
On Fri, 2009-05-08 at 14:28 -0400, Mike Frysinger wrote:
> On Friday 08 May 2009 10:50:54 Peter Griffin wrote:
> > >From 2652ec6503dbe78e5bf371b77544e168166aa57d Mon Sep 17 00:00:00 2001
> >
> > From: Peter Griffin <pgriffin@mpc-data.co.uk>
> > Date: Fri, 8 May 2009 15:01:21 +0100
> > Subject: [PATCH] Add ptrace support for NOMMU debugging
>
> are you not using git-send-email ? posting the actual file produced by git-
> format-patch looks weird (not sure if git-am works with this).
Hi Mike,
I was using git-format-patch to generate the patches, and then evolution
in 'pre-format' mode to insert the patch file and send the email.
I've not used git-send-email before, but I just installed it on my
system and it looks really good. I especially like the look of the
--signed-off-by-cc option :-)
> > + else if ( addr = PT_TEXT_ADDR)
> > + tmp = child->mm->start_code;
> > + else if ( addr = PT_DATA_ADDR)
> > + tmp = child->mm->start_data;
> > + else if ( addr = PT_TEXT_END_ADDR )
> > + tmp = child->mm->end_code;
> > + else if ( addr = PT_TEXT_LEN )
> > + tmp = child->mm->end_code - child->mm->start_code;
>
> style wrong: no space inside of those parenthesis
> -mike
Noted, thanks for pointing it out. Paul fixed this for me when
committing.
regards,
Peter.
prev parent reply other threads:[~2009-05-12 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 14:50 [PATCH] Add ptrace support for NOMMU debugging Peter Griffin
2009-05-08 18:28 ` Mike Frysinger
2009-05-12 8:38 ` Peter Griffin [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=1242117531.32597.17.camel@quercus-bis \
--to=pgriffin@mpc-data.co.uk \
--cc=linux-sh@vger.kernel.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