From: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
To: Pedro Alves <palves@redhat.com>, arnez@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PING] [PATCH 00/11] Regset rework preparations part 1
Date: Thu, 22 May 2014 07:28:00 -0000 [thread overview]
Message-ID: <537DA72D.4080600@linux.vnet.ibm.com> (raw)
In-Reply-To: <537C8241.20909@redhat.com>
On 05/21/2014 12:38 PM, Pedro Alves wrote:
> On 05/19/2014 08:32 AM, Andreas Arnez wrote:
>> On Thu, May 15 2014, Andreas Arnez wrote:
>>
>>> This is the first half of the "regset rework preparations" series I've
>>> posted as RFC:
>>> https://sourceware.org/ml/gdb-patches/2014-04/msg00560.html
>>
>> 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.
>>>
>>>> Patches 3, 4, 6, 7, 8 (AARCH64, ARM, MIPS, MN10300, and SCORE): No
>>>> comments yet.
>>>>
>>>>> * Patch 9 ("SPARC: Rename register maps from "*regset" to "*regmap"):
>>>>> Adjusts naming, to avoid name clashes in patch 10.
>>>>
>>>> Approved by Mark Kettenis:
>>>> https://sourceware.org/ml/gdb-patches/2014-05/msg00038.html
>>>
>>> I don't really expect any response for MN10300 and SCORE. I'd give it
>>> a few days to give people with an interest in ARM and MIPS the
>>> opportunity to repsond, but feel free to move ahead with 3, 4, 6, 7
>>> and 8 after that.
>>
>> As suggested, I've waited a few additional days now for comments on
>> patches 3, 4, 6, 7, and 8. Apart from those I believe everything else
>> in this series was approved already.
>>
>> OK to push?
>>
>
> I've read the series, and it all looked fine to me.
>
> Please push.
>
Done. Thanks!
-Andreas-
prev parent reply other threads:[~2014-05-22 7:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 15:49 Andreas Arnez
2014-05-15 15:49 ` [PATCH 06/11] MIPS: Replace regset_alloc() invocations by static regset structures Andreas Arnez
2014-05-15 15:49 ` [PATCH 08/11] SCORE: Replace regset_alloc() invocation by a static regset structure Andreas Arnez
2014-05-15 15:49 ` [PATCH 04/11] ARM: Replace regset_alloc() invocations by static regset structures Andreas Arnez
2014-05-15 15:49 ` [PATCH 10/11] SPARC: " Andreas Arnez
2014-05-15 15:49 ` [PATCH 05/11] X86: " Andreas Arnez
2014-05-15 15:49 ` [PATCH 11/11] Drop regset_alloc() Andreas Arnez
2014-05-15 15:49 ` [PATCH 02/11] Remove 'arch' field from regset structure Andreas Arnez
2014-05-15 15:49 ` [PATCH 09/11] SPARC: Rename register maps from "*regset" to "*regmap" Andreas Arnez
2014-05-15 15:49 ` [PATCH 03/11] AARCH64: Replace regset_alloc() invocations by static regset structures Andreas Arnez
2014-05-15 15:50 ` [PATCH 01/11] Constify " Andreas Arnez
2014-05-15 15:59 ` [PATCH 07/11] MN10300: Replace regset_alloc() invocations by static " Andreas Arnez
2014-05-19 7:32 ` [PING] [PATCH 00/11] Regset rework preparations part 1 Andreas Arnez
2014-05-20 20:41 ` Maciej W. Rozycki
2014-05-21 10:39 ` Pedro Alves
2014-05-22 7:28 ` Andreas Krebbel [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=537DA72D.4080600@linux.vnet.ibm.com \
--to=krebbel@linux.vnet.ibm.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).