From: Kris Van Hees <kris.van.hees@oracle.com>
To: Sam James <sam@gentoo.org>
Cc: dtrace@lists.linux.dev
Subject: Re: [PATCH] cmd: drop legacy DTrace references
Date: Thu, 3 Oct 2024 14:27:35 -0400 [thread overview]
Message-ID: <Zv7iF6uNrsrIv5xe@oracle.com> (raw)
In-Reply-To: <66555d41665c9ed4e1cae5428739316ad8a2cb03.1724985747.git.sam@gentoo.org>
On Fri, Aug 30, 2024 at 03:42:27AM +0100, Sam James wrote:
> We don't have a kernel module anymore.
>
> Signed-off-by: Sam James <sam@gentoo.org>
Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>
> ---
> cmd/dtrace.8 | 9 ---------
> 1 file changed, 9 deletions(-)
>
> diff --git a/cmd/dtrace.8 b/cmd/dtrace.8
> index 44382e1e..d82ed209 100644
> --- a/cmd/dtrace.8
> +++ b/cmd/dtrace.8
> @@ -181,15 +181,6 @@ Print CTF type library debugging output on standard error.
> Set a given DTrace option.
>
> Options set this way are overridden both by options specified via \fB-x\fR on the command line, and by \fBsetopt\fR statements.
> -.IP DTRACE_MODULES_CONF
> -The location of the file containing names of kernel modules to load (see below).
> -If unset, \fB/etc/dtrace-modules\fR.
> -
> -.SH "FILES"
> -.LP
> -The following files are consulted:
> -.IP /etc/dtrace-modules
> -A list of kernel module names, one per line, which are loaded in addition to \fBdtrace.ko\fR if the \fBdtrace\fR device is not found. (Failure to load these modules is not an error.)
>
> .SH SEE ALSO
> .BR cpp (1),
> --
> 2.46.0
>
prev parent reply other threads:[~2024-10-03 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 2:42 [PATCH] cmd: drop legacy DTrace references Sam James
2024-10-03 18:27 ` 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=Zv7iF6uNrsrIv5xe@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=sam@gentoo.org \
/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