Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Core regset support for Linux/SPARC.
Date: Sat, 08 Apr 2006 20:30:00 -0000	[thread overview]
Message-ID: <20060408203040.GB18707@nevyn.them.org> (raw)
In-Reply-To: <20060406.145119.102460789.davem@davemloft.net>

On Thu, Apr 06, 2006 at 02:51:19PM -0700, David S. Miller wrote:
> 
> Thankfully the Sparc target layer already had nice generic
> support for this, so it was merely a matter of defining some
> offsets and some small helper stubs.

Yes indeed.  Thanks to Mark for his usual thorough job there :-)

> Ok to apply?
 
> 2006-04-06  David S. Miller  <davem@sunset.davemloft.net>
> 
> 	* sparc64-linux-tdep.c (sparc64_linux_core_gregset,
> 	sparc64_linux_supply_core_gregset,
> 	sparc64_linux_collect_core_gregset,
> 	sparc64_linux_supply_core_fpregset,
> 	sparc64_linux_collect_core_fpregset): New.
> 	(sparc64_linux_init_abi): Register them with generic sparc
> 	core regset infrastructure.
> 	* sparc32-linux-tdep.c (sparc32_linux_core_gregset,
> 	sparc32_linux_supply_core_gregset,
> 	sparc32_linux_collect_core_gregset,
> 	sparc32_linux_supply_core_fpregset,
> 	sparc32_linux_collect_core_fpregset): New.
> 	(sparc32_linux_init_abi): Register them with generic sparc
> 	core regset infrastructure.
> 	* Makefile.in: Update dependencies.

Yes, this looks fine.  Thanks.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-08 20:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 21:52 David S. Miller
2006-04-08 20:30 ` Daniel Jacobowitz [this message]
2006-04-08 21:16   ` David S. Miller

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=20060408203040.GB18707@nevyn.them.org \
    --to=drow@false.org \
    --cc=davem@davemloft.net \
    --cc=gdb-patches@sources.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