public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: arnez@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PING^2] [RFC 00/23] Regset rework preparations
Date: Wed, 14 May 2014 12:27:00 -0000	[thread overview]
Message-ID: <201405141227.s4ECRggr005736@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <87fvkc8snt.fsf@br87z6lw.de.ibm.com> (message from Andreas Arnez	on Wed, 14 May 2014 14:13:26 +0200)

> 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.

  reply	other threads:[~2014-05-14 12:27 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 [this message]
2014-07-03 16:08   ` Andreas Arnez

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=201405141227.s4ECRggr005736@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=arnez@linux.vnet.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).