From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCHv2 1/2] gdb/python: Reuse gdb.RegisterDescriptor objects where possible
Date: Wed, 22 Jul 2020 16:10:40 +0100 [thread overview]
Message-ID: <20200722151040.GG853475@embecosm.com> (raw)
In-Reply-To: <31010379-0716-02c5-b236-52e8ccfd5919@palves.net>
* Pedro Alves <pedro@palves.net> [2020-07-22 15:32:40 +0100]:
> On 7/22/20 3:05 PM, Andrew Burgess wrote:
> > * Pedro Alves <pedro@palves.net> [2020-07-22 14:10:17 +0100]:
> >
> >> Hi Andrew,
> >>
>
> Hi Andrew,
>
> > Thanks for your feedback. As this patch was already merged, the patch
> > below applies on top of current master to address these issues.
>
> Sorry, I didn't realize it was already in.
Not a problem. Always happy to get feedback on how to improve
patches.
>
> >
> > If I don't hear anything I'll apply this in a couple of days.
>
> It looks great. Please merge it.
Done.
Thanks,
Andrew
next prev parent reply other threads:[~2020-07-22 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 8:48 [PATCH 0/2] Improvements to Python Register Descriptor API Andrew Burgess
2020-07-08 8:48 ` [PATCH 1/2] gdb/python: Reuse gdb.RegisterDescriptor objects where possible Andrew Burgess
2020-07-13 18:21 ` Tom Tromey
2020-07-08 8:48 ` [PATCH 2/2] gdb/python: Reuse gdb.RegisterGroup " Andrew Burgess
2020-07-13 18:23 ` Tom Tromey
2020-07-14 17:14 ` [PATCHv2 0/2] Improvements to Python Register Descriptor API Andrew Burgess
2020-07-14 17:14 ` [PATCHv2 1/2] gdb/python: Reuse gdb.RegisterDescriptor objects where possible Andrew Burgess
2020-07-22 13:10 ` Pedro Alves
2020-07-22 14:05 ` Andrew Burgess
2020-07-22 14:32 ` Pedro Alves
2020-07-22 15:10 ` Andrew Burgess [this message]
2020-07-14 17:14 ` [PATCHv2 2/2] gdb/python: Reuse gdb.RegisterGroup " Andrew Burgess
2020-07-21 18:26 ` [PATCHv2 0/2] Improvements to Python Register Descriptor API Tom Tromey
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=20200722151040.GG853475@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=tom@tromey.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