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: [PATCH v2 3/3] doc: Clean up list of unimplemented functions
Date: Fri, 19 Dec 2025 15:52:46 -0500	[thread overview]
Message-ID: <aUW7Ht8zDQ9H9HWc@oracle.com> (raw)
In-Reply-To: <20251219173636.16078-1-eugene.loh@oracle.com>

On Fri, Dec 19, 2025 at 12:36:36PM -0500, eugene.loh@oracle.com wrote:
> From: Eugene Loh <eugene.loh@oracle.com>
> 
> The case of dpath is tricky.  First, it is actually called d_path() and
> it was always meant to be used internally.  Further, it is in fact
> implemented, but only as a stub that always returns "<unknown>".  Just
> remove it from this listing and remain silent on it.
> 
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>

Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>

> ---
>  doc/userguide/reference/unimplemented_functions.md | 13 -------------
>  1 file changed, 13 deletions(-)
> 
> diff --git a/doc/userguide/reference/unimplemented_functions.md b/doc/userguide/reference/unimplemented_functions.md
> index f69600b56..5f30c9385 100644
> --- a/doc/userguide/reference/unimplemented_functions.md
> +++ b/doc/userguide/reference/unimplemented_functions.md
> @@ -6,25 +6,12 @@ and some functions are not relevant to Linux and might never be implemented.
>  The following functions are not currently implemented:
>  
>  -   `breakpoint`
> -
>  -   `chill`
> -
> --   `dpath`
>  -   `ddi_pathname`
> -
> --   `inet_ntoa6`
> -
> --   `inet_ntop`
> -
>  -   `msgdsize`
> -
>  -   `msgsize`
> -
>  -   `panic`
> -
>  -   `pcap`
> -
>  -   `stop`
>  
> -
>  **Parent topic:**[DTrace Function Reference](../reference/dtrace_functions.md)
> -- 
> 2.47.3
> 

      reply	other threads:[~2025-12-19 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 17:36 [PATCH v2 3/3] doc: Clean up list of unimplemented functions eugene.loh
2025-12-19 20:52 ` 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=aUW7Ht8zDQ9H9HWc@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