From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING^2] [RFC 00/23] Regset rework preparations
Date: Thu, 03 Jul 2014 16:08:00 -0000 [thread overview]
Message-ID: <87vbrefmre.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <201405141227.s4ECRggr005736@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Wed, 14 May 2014 14:27:42 +0200 (CEST)")
On Wed, May 14 2014, Mark Kettenis wrote:
>> From: Andreas Arnez <arnez@linux.vnet.ibm.com>
>> Date: Wed, 14 May 2014 14:13:26 +0200
>>
>> Although there was feedback for some of the patches in this series
>> (https://sourceware.org/ml/gdb-patches/2014-04/msg00560.html), many are
>> still uncommented. I'd really appreciate more feedback, particularly
>> for the architecture-specific changes.
>
> Sorry, I've not been able to find time to process your reply on my
> review of patch 12 yet and won't be able to for the next 1.5 weeks or
> so. But perhaps you could move ahead with the diffs that don't depend
> on that one which seem useful in their own right.
Mark, I've done the split as suggested, and the first part is upstream
since May 22nd. "Patch 12" has become patch 2 in the second part,
"regset rework preparations part 2":
https://sourceware.org/ml/gdb-patches/2014-06/msg00881.html
Are there any further comments on this series? Or is it ready to push?
prev parent reply other threads:[~2014-07-03 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 12:13 Andreas Arnez
2014-05-14 12:27 ` Mark Kettenis
2014-07-03 16:08 ` Andreas Arnez [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=87vbrefmre.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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).