Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: brobecker@adacore.com (Joel Brobecker)
Cc: gdb-patches@sourceware.org
Subject: Re: [1/3] Remove gdbarch-swapping of remote_address_masked
Date: Thu, 14 Jun 2007 13:04:00 -0000	[thread overview]
Message-ID: <200706141304.l5ED44ZI028430@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070613190308.GA21293@adacore.com> from "Joel Brobecker" at Jun 13, 2007 12:03:08 PM

Joel Brobecker wrote:

> I just noticed by accident that there is a declaration of this
> function that should be removed as well:
> 
>     static void build_remote_gdbarch_data (void);

Ah, thanks.  I've updated my patch accordingly.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2007-06-14 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 23:22 Ulrich Weigand
2007-06-11 18:03 ` Jim Blandy
2007-06-12 16:14   ` Ulrich Weigand
2007-06-12 15:34 ` Daniel Jacobowitz
2007-06-13 19:01 ` Joel Brobecker
2007-06-14 13:04   ` Ulrich Weigand [this message]
2007-06-22 12:52 ` Ulrich Weigand

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=200706141304.l5ED44ZI028430@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.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