public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: cbiesinger@chromium.org
To: gdb-patches@sourceware.org
Cc: Christian Biesinger <cbiesinger@google.com>
Subject: [PATCH 3/3] Make the class name in the definition match the declaration
Date: Fri, 24 Jan 2020 14:15:00 -0000	[thread overview]
Message-ID: <20200124141458.171392-4-cbiesinger@chromium.org> (raw)
In-Reply-To: <20200124141458.171392-1-cbiesinger@chromium.org>

From: Christian Biesinger <cbiesinger@google.com>

Fixes a compile error because the class is actually called
arm_netbsd_nat_target.

gdb/ChangeLog:

2020-01-24  Christian Biesinger  <cbiesinger@google.com>

	* arm-nbsd-nat.c (arm_nbsd_nat_target::fetch_registers): Rename to...
	(arm_netbsd_nat_target::fetch_registers): ...this.
	(arm_nbsd_nat_target::store_registers): Rename to...
	(arm_netbsd_nat_target::store_registers): ...this.

Change-Id: Ibebfab9edeff48f54c32d0745afda1d74d31de92
---
 gdb/arm-nbsd-nat.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/arm-nbsd-nat.c b/gdb/arm-nbsd-nat.c
index 31fe66c724..5072bd09ec 100644
--- a/gdb/arm-nbsd-nat.c
+++ b/gdb/arm-nbsd-nat.c
@@ -191,7 +191,7 @@ fetch_fp_regs (struct regcache *regcache)
 }
 
 void
-arm_nbsd_nat_target::fetch_registers (struct regcache *regcache, int regno)
+arm_netbsd_nat_target::fetch_registers (struct regcache *regcache, int regno)
 {
   if (regno >= 0)
     {
@@ -380,7 +380,7 @@ store_fp_regs (const struct regcache *regcache)
 }
 
 void
-arm_nbsd_nat_target::store_registers (struct regcache *regcache, int regno)
+arm_netbsd_nat_target::store_registers (struct regcache *regcache, int regno)
 {
   if (regno >= 0)
     {
-- 
2.25.0.341.g760bfbb309-goog

  reply	other threads:[~2020-01-24 14:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 14:15 [PATCH 0/3] Fix some ARM NetBSD compile errors cbiesinger
2020-01-24 14:15 ` cbiesinger [this message]
2020-01-24 14:54   ` [PATCH 3/3] Make the class name in the definition match the declaration Kamil Rytarowski
2020-01-24 15:06   ` Tom Tromey
2020-01-24 15:49     ` Christian Biesinger via gdb-patches
2020-01-24 14:15 ` [PATCH 1/3] Support the NetBSD version of pthread_setname_np cbiesinger
2020-01-24 14:59   ` Kamil Rytarowski
2020-01-24 15:04   ` Tom Tromey
2020-01-24 14:18 ` [PATCH 2/3] Define _KMEMUSER in arm-nbsd-nat.c cbiesinger
2020-01-24 14:22   ` [PATCH 2/3 v2] " cbiesinger
2020-01-24 14:32     ` Kamil Rytarowski
2020-01-24 14:34       ` Christian Biesinger via gdb-patches
2020-01-24 14:36         ` [PATCH v3 2/3] Define _KERNTYPES " cbiesinger
2020-01-24 15:04           ` Tom Tromey
2020-01-24 14:58       ` [PATCH 2/3 v2] Define _KMEMUSER " Christian Biesinger via gdb-patches
2020-01-24 15:36         ` Kamil Rytarowski
2020-01-24 15:37           ` Christian Biesinger via gdb-patches
2020-01-24 15:49             ` Kamil Rytarowski
2020-01-24 16:25               ` Christian Biesinger via gdb-patches
2020-01-24 16:45                 ` Kamil Rytarowski
2020-01-27 21:28                   ` Christian Biesinger via gdb-patches
2020-02-05 18:02                     ` Christian Biesinger via gdb-patches
2020-02-06 13:25                       ` Kamil Rytarowski
2020-02-06 13:19                     ` Kamil Rytarowski

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=20200124141458.171392-4-cbiesinger@chromium.org \
    --to=cbiesinger@chromium.org \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).