Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Linux/gdbserver: Clean up fetch_register and store_register
Date: Tue, 06 Dec 2011 23:20:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1112062309120.6710@tp.orcam.me.uk> (raw)
In-Reply-To: <201112061914.41661.pedro@codesourcery.com>

On Tue, 6 Dec 2011, Pedro Alves wrote:

> >  No regressions on i686-linux-gnu or mips-linux-gnu (like with the 
> > previous change I had to force srv_linux_regsets to "no" and deal with 
> > some bitrot of that configuration to get indicative results).  OK to 
> > apply?
> 
> Okay.  Thanks.
> 
> > 2011-11-22  Maciej W. Rozycki  <macro@codesourcery.com>
> > 
> > 	gdb/gdbserver/
> > 	* linux-low.c (fetch_register, store_register): Make code
> > 	consistent, fix formatting.

 This one applied now too, thanks.

  Maciej


      reply	other threads:[~2011-12-06 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 16:08 Maciej W. Rozycki
2011-12-06 19:33 ` Pedro Alves
2011-12-06 23:20   ` Maciej W. Rozycki [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=alpine.DEB.1.10.1112062309120.6710@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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