From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH v5 1/6] usdt: get arg types and xlations into DTrace from the DOF
Date: Tue, 05 Nov 2024 19:53:04 +0000 [thread overview]
Message-ID: <87bjytfof3.fsf@esperi.org.uk> (raw)
In-Reply-To: <ZypdcfLQrWI+osnV@oracle.com> (Kris Van Hees's message of "Tue, 5 Nov 2024 13:01:21 -0500")
On 5 Nov 2024, Kris Van Hees stated:
> Reviewed-by withdrawn - see my comments on patch 4/6 (that one contains a diff
> that belongs in this patch).
Bah! Fixed.
--
NULL && (void)
next prev parent reply other threads:[~2024-11-05 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 0:06 [PATCH v5 0/6] usdt typed args, translators and arg mapping Nick Alcock
2024-11-05 0:06 ` [PATCH v5 1/6] usdt: get arg types and xlations into DTrace from the DOF Nick Alcock
2024-11-05 16:56 ` Kris Van Hees
2024-11-05 18:01 ` [DTrace-devel] " Kris Van Hees
2024-11-05 19:53 ` Nick Alcock [this message]
2024-11-05 0:06 ` [PATCH v5 2/6] dtprobed: stop skipping zero-tracepoint probes in dof_stash.c Nick Alcock
2024-11-05 0:06 ` [PATCH v5 3/6] cg: add argument mapping in the trampoline Nick Alcock
2024-11-05 17:29 ` Kris Van Hees
2024-11-05 19:58 ` Nick Alcock
2024-11-05 0:06 ` [PATCH v5 4/6] usdt: typed args and arg mapping Nick Alcock
2024-11-05 18:53 ` Kris Van Hees
2024-11-06 11:16 ` Nick Alcock
2024-11-06 22:18 ` Kris Van Hees
2024-11-05 0:06 ` [PATCH v5 5/6] usdt: new tests for USDT arg sanity with overlapping pid probes Nick Alcock
2024-11-05 0:06 ` [PATCH v5 6/6] usdt: fix create_underlying error path Nick Alcock
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=87bjytfof3.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.