Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	Eli Zaretskii <eliz@gnu.org>,
	       gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Implement support for PowerPC BookE masked and ranged watchpoints
Date: Tue, 23 Nov 2010 22:05:00 -0000	[thread overview]
Message-ID: <1290549884.3164.54.camel@hactar> (raw)
In-Reply-To: <20101120045951.GN2634@adacore.com>

On Fri, 2010-11-19 at 20:59 -0800, Joel Brobecker wrote:
> > Changed to:
> > 
> > +The watchpoint will stop execution of the inferior whenever it\n\
> > +writes to any address within the [start-address, end-address] range\n\
> > +(including start-address and end-address)."));
> 
> Can you move the "writes" to the line before? This is to prevent
> breaking line between the subject and the verb, making it easier
> for the user to read...

Ok. Fixed in the patch I just posted.

> > Previous patches in this series also used this style and were accepted,
> > so there's currently code like that in ppc-linux-nat.c in CVS HEAD
> > (e.g., ppc_linux_{insert,remove}_hw_breakpoint,
> > ppc_linux_{insert,remove}_watchpoint). Should I keep this patch like
> > this for consistency, or change this patch and the existing instances?
> 
> You'll have to excuse us, because not all of us are aware of the entire
> coding standard used in GDB.  It makes me want to revive the idea of
> a Wiki page, because I need some kind of table/list to remind me of
> all of them.  If it's against the CS, then I'd just fix the instances
> there, and let anyone changing the code on the other instances worry
> about that (or you can do that already as an (obvious) separate patch).

No problem. I fixed the whitespace in my patch. I'll commit a separate
obvious patch later then.
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


      reply	other threads:[~2010-11-23 22:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 19:42 Thiago Jung Bauermann
2010-10-07 14:48 ` Thiago Jung Bauermann
2010-10-23  4:23 ` Thiago Jung Bauermann
2010-10-23  9:07   ` Eli Zaretskii
2010-10-30  1:59     ` Thiago Jung Bauermann
2010-10-30  7:13       ` Eli Zaretskii
2010-11-01 21:47         ` Thiago Jung Bauermann
2010-11-02  3:53           ` Eli Zaretskii
2010-11-04 21:12             ` Thiago Jung Bauermann
2010-11-16  4:01               ` Jan Kratochvil
2010-11-18 17:26                 ` Joel Brobecker
2010-11-19 19:55                 ` Thiago Jung Bauermann
2010-11-19 23:45                   ` Joel Brobecker
2010-11-22 17:04                     ` Thiago Jung Bauermann
2010-11-22 17:38                       ` Joel Brobecker
2010-11-22 17:46                         ` Jan Kratochvil
2010-11-22 18:37                           ` Joel Brobecker
2010-11-20  5:00                   ` Joel Brobecker
2010-11-23 22:05                     ` Thiago Jung Bauermann [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=1290549884.3164.54.camel@hactar \
    --to=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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