public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
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: [DTrace-devel] [PATCH 1/2] Fix comments in rawtp provider
Date: Fri, 19 Dec 2025 01:11:22 -0500	[thread overview]
Message-ID: <aUTsiknMoqQU4kR8@oracle.com> (raw)
In-Reply-To: <20251208054114.28036-1-eugene.loh@oracle.com>

On Mon, Dec 08, 2025 at 12:41:13AM -0500, eugene.loh--- via DTrace-devel 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_prov_rawtp.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/libdtrace/dt_prov_rawtp.c b/libdtrace/dt_prov_rawtp.c
> index a36bb51f4..709f7040f 100644
> --- a/libdtrace/dt_prov_rawtp.c
> +++ b/libdtrace/dt_prov_rawtp.c
> @@ -118,9 +118,9 @@ static int populate(dtrace_hdl_t *dtp)
>  }
>  
>  /*
> - * Generate a BPF trampoline for a SDT probe.
> + * Generate a BPF trampoline for a rawtp probe.
>   *
> - * The trampoline function is called when a SDT probe triggers, and it must
> + * The trampoline function is called when a rawtp probe triggers, and it must
>   * satisfy the following prototype:
>   *
>   *	int dt_rawtp(void *data)
> -- 
> 2.47.3
> 
> 
> _______________________________________________
> DTrace-devel mailing list
> DTrace-devel@oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/dtrace-devel

      parent reply	other threads:[~2025-12-19  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  5:41 [PATCH 1/2] Fix comments in rawtp provider eugene.loh
2025-12-08  5:41 ` [PATCH 2/2] doc: Update the sdt provider documentation eugene.loh
2025-12-19  6:11 ` 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=aUTsiknMoqQU4kR8@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