From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH v2 1/4] cg, providers: refactor clearing probe arguments
Date: Thu, 18 Dec 2025 15:20:32 -0500 [thread overview]
Message-ID: <aURiEFMIDadxcjJ/@oracle.com> (raw)
In-Reply-To: <126eae26-5a12-f977-cf3d-7efe87f9b26b@oracle.com>
On Thu, Dec 18, 2025 at 02:43:23PM -0500, Eugene Loh wrote:
> This looks like v1...
Woops, sent from wrong system. real-v2 posted
>
> On 12/18/25 14:31, Kris Van Hees via DTrace-devel wrote:
prev parent reply other threads:[~2025-12-18 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 19:31 [PATCH v2 1/4] cg, providers: refactor clearing probe arguments Kris Van Hees
2025-12-18 19:43 ` [DTrace-devel] " Eugene Loh
2025-12-18 20:20 ` 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=aURiEFMIDadxcjJ/@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