Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedromfc@linux.ibm.com (Pedro Franco de Carvalho)
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] [PowerPC] Move up some register access routines
Date: Thu, 08 Aug 2019 16:25:00 -0000	[thread overview]
Message-ID: <20190808162508.B56C8D802EF@oc3748833570.ibm.com> (raw)
In-Reply-To: <20190726125012.6503-3-pedromfc@linux.ibm.com> from "Pedro Franco de Carvalho" at Jul 26, 2019 09:50:11 AM

Pedro Franco de Carvalho wrote:

> 	* ppc-linux-nat.c (ppc_linux_nat_target::store_registers)
> 	(ppc_linux_nat_target::auxv_parse)
> 	(ppc_linux_nat_target::read_description)
> 	(supply_gregset, fill_gregset, supply_fpregset, fill_fpregset):
> 	Move up.

This is OK.

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


      reply	other threads:[~2019-08-08 16:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 12:50 [PATCH 0/3] low_new_clone in linux-nat.c and powerpc watchpoint fixes Pedro Franco de Carvalho
2019-07-26 12:50 ` [PATCH 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat Pedro Franco de Carvalho
2019-08-08 16:24   ` Ulrich Weigand
2019-08-08 20:27     ` Pedro Franco de Carvalho
2019-08-09 11:04       ` Ulrich Weigand
2019-08-09 15:04         ` Pedro Franco de Carvalho
2019-08-09 15:28           ` Ulrich Weigand
2019-08-09 15:53             ` Pedro Franco de Carvalho
2019-07-26 12:50 ` [PATCH 1/3] Add low_new_clone method to linux_nat_target Pedro Franco de Carvalho
2019-08-08 14:05   ` Ulrich Weigand
2019-07-26 12:50 ` [PATCH 2/3] [PowerPC] Move up some register access routines Pedro Franco de Carvalho
2019-08-08 16:25   ` Ulrich Weigand [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=20190808162508.B56C8D802EF@oc3748833570.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedromfc@linux.ibm.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