From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [commit] gdb_byte regcache.[hc]
Date: Fri, 17 Jun 2005 01:45:00 -0000 [thread overview]
Message-ID: <20050617014520.GA17013@nevyn.them.org> (raw)
In-Reply-To: <7541.192.87.1.200.1118854079.squirrel@192.87.1.200>
On Wed, Jun 15, 2005 at 06:47:59PM +0200, Mark Kettenis wrote:
> >>
> >> Argh, let's blame it on my jetlag, but I meant regcache_raw_supply and
> >> regcache_raw_collect as the function that should take `void *' instead
> >> of `gdb_byte *'. The other regcache_raw_xxx functions can stay as
> >> they are now.
> >
> > 6hrs time difference is not jetlag ...
> >
> > Just supply/collect is making more sense :-)
>
> The attached patchis what I had in mind.
>
> OK?
I think this is a good idea.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-17 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 17:07 Andrew Cagney
2005-05-19 18:56 ` Daniel Jacobowitz
2005-05-19 19:13 ` Andrew Cagney
2005-06-10 22:12 ` Mark Kettenis
2005-06-11 1:43 ` Michael Snyder
2005-06-11 21:29 ` Mark Kettenis
2005-06-15 15:48 ` Andrew Cagney
2005-06-15 16:48 ` Mark Kettenis
2005-06-17 1:45 ` Daniel Jacobowitz [this message]
2005-06-18 15:24 ` Mark Kettenis
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=20050617014520.GA17013@nevyn.them.org \
--to=drow@false.org \
--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