From: Simon Marchi <simon.marchi@polymtl.ca>
To: Luis Machado <luis.machado@arm.com>, gdb-patches@sourceware.org
Cc: thiago.bauermann@linaro.org
Subject: Re: [PATCH v6 13/17] [gdb/generic] Get rid of linux-core-thread-data
Date: Wed, 13 Sep 2023 10:10:13 -0400 [thread overview]
Message-ID: <c3c6893f-08a1-4507-a941-6bbf6e4fcf11@polymtl.ca> (raw)
In-Reply-To: <20230913101815.178154-14-luis.machado@arm.com>
On 9/13/23 06:18, Luis Machado wrote:
> This struct type seems to have been used in the past as a callback
> parameter. Now it seems that case is no longer true, so we can simplify
> things by passing the individual parameters linux_core_thread_data
> encapsulates directly to the functions.
>
> This is just a cleanup before the next change.
Thanks, LGTM.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Simon
next prev parent reply other threads:[~2023-09-13 14:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 10:17 [PATCH v6 00/17] SME support for AArch64 gdb/gdbserver on Linux Luis Machado
2023-09-13 10:17 ` [PATCH v6 01/17] [gdb/aarch64] Fix register fetch/store order for native AArch64 Linux Luis Machado
2023-09-13 10:18 ` [PATCH v6 02/17] [gdb/aarch64] refactor: Rename SVE-specific files Luis Machado
2023-09-13 10:18 ` [PATCH v6 03/17] [gdb/gdbserver] refactor: Simplify SVE interface to read/write registers Luis Machado
2023-09-13 10:18 ` [PATCH v6 04/17] [gdb/aarch64] sve: Fix return command when using V registers in a SVE-enabled target Luis Machado
2023-09-13 10:18 ` [PATCH v6 05/17] [gdb/aarch64] sme: Enable SME registers and pseudo-registers Luis Machado
2023-09-13 10:18 ` [PATCH v6 06/17] [gdbserver/generic] Convert tdesc's expedite_regs to a string vector Luis Machado
2023-09-13 15:28 ` Tom Tromey
2023-09-13 10:18 ` [PATCH v6 07/17] [gdbserver/aarch64] refactor: Adjust expedited registers dynamically Luis Machado
2023-09-13 10:18 ` [PATCH v6 08/17] [gdbserver/aarch64] sme: Add support for SME Luis Machado
2023-09-13 10:18 ` [PATCH v6 09/17] [gdb/aarch64] sve: Fix signal frame z/v register restore Luis Machado
2023-09-13 10:18 ` [PATCH v6 10/17] [gdb/aarch64] sme: Signal frame support Luis Machado
2023-09-13 10:18 ` [PATCH v6 11/17] [gdb/aarch64] sme: Fixup sigframe gdbarch when vg/svg changes Luis Machado
2023-09-13 10:18 ` [PATCH v6 12/17] [gdb/aarch64] sme: Support TPIDR2 signal frame context Luis Machado
2023-09-13 10:18 ` [PATCH v6 13/17] [gdb/generic] Get rid of linux-core-thread-data Luis Machado
2023-09-13 14:10 ` Simon Marchi [this message]
2023-09-13 10:18 ` [PATCH v6 14/17] [gdb/generic] corefile/bug: Use thread-specific gdbarch when dumping register state to core files Luis Machado
2023-09-13 14:20 ` Simon Marchi
2023-09-13 15:11 ` Tom Tromey
2023-09-13 10:18 ` [PATCH v6 15/17] [gdb/aarch64] sme: Core file support for Linux Luis Machado
2023-09-13 10:18 ` [PATCH v6 16/17] [gdb/testsuite] sme: Add SVE/SME testcases Luis Machado
2023-09-13 14:34 ` Simon Marchi
2023-09-13 14:46 ` Luis Machado
2023-09-13 15:26 ` Simon Marchi
2023-09-13 10:18 ` [PATCH v6 17/17] [gdb/docs] sme: Document SME registers and features Luis Machado
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=c3c6893f-08a1-4507-a941-6bbf6e4fcf11@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=thiago.bauermann@linaro.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).