From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: gdb-patches@sourceware.org
Cc: uweigand@de.ibm.com, edjunior@gmail.com, palves@redhat.com
Subject: Re: [PATCH v4 00/12] GDB support for more powerpc registers on linux
Date: Thu, 16 Aug 2018 16:46:00 -0000 [thread overview]
Message-ID: <87wosqntwa.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180815000608.26840-1-pedromfc@linux.ibm.com>
Pedro Franco de Carvalho <pedromfc@linux.ibm.com> writes:
> These are all the changes compared to V2, following the suggestions
> there, and following the changes to linux-tdep.c:
>
> * Adapted "Zero-initialize linux note sections" due to recent changes
> from commit a616bb9450.
>
> * Added a comment to "Zero-initialize linux note sections"
>
> * Adapted all the four main patches that enable the registers
> (PPR/DSCR, TAR, EBB/PMU and HTM) to account for the changes from
> commit a616bb9450.
>
> * De-duplicated testcase names. Changed a few of the test names so
> that they are environment-independent. Fixed a few other minor
> issues with the testcases.
>
> * Changed one of the testcases for the HTM registers so that it
> XFAILs. This testcase occasionally failed, possibly due to a kernel
> bug.
>
> * Fixed some of the formatting and const-correctness in "[PowerPC] Add
> support for HTM registers", in gdbserver/linux-ppc-low.c.
>
> * Added an item in the NEWS file on the last commit, indicating all
> the newly supported registers from this series.
Considering Ulrich had already approved the V2 patches, do these changes
need to be re-approved, or can they be considered as obvious, and can I
commit them?
I don't know if a NEWS item counts as obvious, but if not, I can submit
it in a separate patch.
Thanks!
--
Pedro Franco de Carvalho
next prev parent reply other threads:[~2018-08-16 16:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 0:07 Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 02/12] [PowerPC] Don't zero-initialize vector register buffers Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 05/12] [PowerPC] Fix two if statements in gdb/ppc-linux-nat.c Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 11/12] [PowerPC] Reject tdescs with VSX and no FPU or Altivec Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 01/12] Zero-initialize linux note sections Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 04/12] [PowerPC] Remove rs6000_pseudo_register_reggroup_p Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 10/12] [PowerPC] Add support for EBB and PMU registers Pedro Franco de Carvalho
2018-08-16 16:51 ` Pedro Alves
2018-08-16 18:16 ` Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 03/12] Add decfloat registers to float reggroup Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 07/12] [PowerPC] Refactor have_ initializers in rs6000-tdep.c Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 06/12] [PowerPC] Fix indentation in arch/ppc-linux-common.c Pedro Franco de Carvalho
2018-08-15 0:07 ` [PATCH v4 09/12] [PowerPC] Add support for TAR Pedro Franco de Carvalho
2018-08-15 0:55 ` [PATCH v4 12/12] [PowerPC] Add support for HTM registers Pedro Franco de Carvalho
2018-08-16 16:53 ` Pedro Alves
2018-08-16 17:50 ` Pedro Franco de Carvalho
2018-08-16 20:16 ` Pedro Franco de Carvalho
2018-08-16 23:47 ` Pedro Franco de Carvalho
2018-08-17 18:11 ` Pedro Alves
2018-08-17 19:25 ` Pedro Franco de Carvalho
2018-08-15 1:16 ` [PATCH v4 08/12] [PowerPC] Add support for PPR and DSCR Pedro Franco de Carvalho
2018-08-16 16:46 ` Pedro Franco de Carvalho [this message]
2018-08-16 17:00 ` [PATCH v4 00/12] GDB support for more powerpc registers on linux Pedro Alves
2018-08-16 17:42 ` Pedro Franco de Carvalho
2018-08-16 18:02 ` Eli Zaretskii
2018-08-16 18:08 ` Pedro Franco de Carvalho
2018-08-16 18:45 ` Eli Zaretskii
2018-08-16 19:23 ` Pedro Franco de Carvalho
2018-10-08 19:09 ` ping: " Jan Kratochvil
2018-10-08 19:32 ` Pedro Franco de Carvalho
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=87wosqntwa.fsf@linux.vnet.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=edjunior@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).