From: Markus Deuling <deuling@de.ibm.com>
To: Maxim Grigoriev <maxim@tensilica.com>
Cc: Markus Deuling <deuling@de.ibm.com>,
GDB Patches <gdb-patches@sourceware.org>,
Ulrich Weigand <uweigand@de.ibm.com>,
Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>,
Jim Blandy <jimb@codesourcery.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [rfc] [00/16] Get rid of current gdbarch
Date: Tue, 09 Oct 2007 05:10:00 -0000 [thread overview]
Message-ID: <470B0CB2.8050303@de.ibm.com> (raw)
In-Reply-To: <470A6EE5.4030104@hq.tensilica.com>
Hi Maxim,
Maxim Grigoriev schrieb:
> Hello, Markus,
>
> I think you missed xtenda-tdep.c.
> First time, you asked for an approval but never checked the patch in.
I still cannot check in patches due to lack of FSF copyright assignment :-( Ulrich checks in my patches and he wasn't available
the last weeks.
> What do you want me to do : to wait until you update it and then test
> it, or just go ahead and do it by myself ?
I did not send the xtensa patches with the new patch set because they're outdated a bit. They dont apply clean anymore and I have to
rework them.
Thank you very much! I'll come up with a new patch set including the xtensa patches soon.
Regards,
Markus
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
prev parent reply other threads:[~2007-10-09 5:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 8:18 Markus Deuling
2007-10-08 13:03 ` Ulrich Weigand
2007-10-08 13:22 ` Markus Deuling
2007-10-08 13:35 ` Daniel Jacobowitz
2007-10-08 14:01 ` Ulrich Weigand
2007-10-08 14:10 ` Daniel Jacobowitz
2007-10-09 20:03 ` Ulrich Weigand
2007-10-09 21:39 ` Daniel Jacobowitz
2007-10-10 11:54 ` Mark Kettenis
2007-10-10 12:01 ` Daniel Jacobowitz
2007-10-08 13:16 ` Joel Brobecker
2007-10-09 7:02 ` Markus Deuling
2007-10-08 17:53 ` Maxim Grigoriev
2007-10-09 5:10 ` Markus Deuling [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=470B0CB2.8050303@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
--cc=maxim@tensilica.com \
--cc=uweigand@de.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