From: Kris Van Hees <kris.van.hees@oracle.com>
To: eugene.loh@oracle.com
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 1/6] Remove unused dpp_pc and dpp_size
Date: Thu, 9 Jan 2025 14:14:15 -0500 [thread overview]
Message-ID: <Z4AgB9v0b1floGXO@oracle.com> (raw)
In-Reply-To: <20241220222716.18511-1-eugene.loh@oracle.com>
On Fri, Dec 20, 2024 at 05:27:11PM -0500, eugene.loh@oracle.com wrote:
> From: Eugene Loh <eugene.loh@oracle.com>
>
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>
> ---
> libdtrace/dt_pid.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/libdtrace/dt_pid.c b/libdtrace/dt_pid.c
> index fd94a0706..2331d1aa7 100644
> --- a/libdtrace/dt_pid.c
> +++ b/libdtrace/dt_pid.c
> @@ -53,9 +53,7 @@ typedef struct dt_pid_probe {
> dev_t dpp_dev;
> ino_t dpp_inum;
> const char *dpp_fname;
> - uintptr_t dpp_pc;
> uintptr_t dpp_vaddr;
> - size_t dpp_size;
> Lmid_t dpp_lmid;
> uint_t dpp_nmatches;
> GElf_Sym dpp_last;
> --
> 2.43.5
>
prev parent reply other threads:[~2025-01-09 19:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 22:27 [PATCH 1/6] Remove unused dpp_pc and dpp_size eugene.loh
2024-12-20 22:27 ` [PATCH 2/6] Use prb instead of psp.pps_prb eugene.loh
2024-12-20 22:27 ` [PATCH 3/6] Simplify references to dtp eugene.loh
2025-01-09 19:21 ` Kris Van Hees
2024-12-20 22:27 ` [PATCH 4/6] Remove unused function arg eugene.loh
2025-01-09 19:17 ` [DTrace-devel] " Kris Van Hees
2024-12-20 22:27 ` [PATCH 5/6] test: Move disassembly and extracting PCs earlier eugene.loh
2024-12-20 22:27 ` [PATCH 6/6] Add support for pid function "-" with absolute offset eugene.loh
2025-01-09 19:12 ` [DTrace-devel] " Kris Van Hees
2025-01-09 20:52 ` Eugene Loh
2025-01-09 21:00 ` Eugene Loh
2025-01-10 5:07 ` Kris Van Hees
2025-01-10 6:30 ` Eugene Loh
2025-01-10 14:47 ` Kris Van Hees
2025-01-09 19:14 ` Kris Van Hees [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=Z4AgB9v0b1floGXO@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.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