summaryrefslogtreecommitdiffstats
path: root/sys/cddl/dev/dtrace
diff options
context:
space:
mode:
authorbrucec <brucec@FreeBSD.org>2011-02-21 09:01:34 +0000
committerbrucec <brucec@FreeBSD.org>2011-02-21 09:01:34 +0000
commit6d9b42b4862ca331b22065d875de9cad9da72658 (patch)
tree1f08a200604ea39c38fc67b8558b5638a6dfba0d /sys/cddl/dev/dtrace
parent879ce9c16d5491279b3bcbf139b4b4a967fb3fab (diff)
downloadFreeBSD-src-6d9b42b4862ca331b22065d875de9cad9da72658.zip
FreeBSD-src-6d9b42b4862ca331b22065d875de9cad9da72658.tar.gz
Fix typos - remove duplicate "the".
PR: bin/154928 Submitted by: Eitan Adler <lists at eitanadler.com> MFC after: 3 days
Diffstat (limited to 'sys/cddl/dev/dtrace')
-rw-r--r--sys/cddl/dev/dtrace/amd64/dtrace_subr.c2
-rw-r--r--sys/cddl/dev/dtrace/i386/dtrace_subr.c2
2 files changed, 2 insertions, 2 deletions
diff --git a/sys/cddl/dev/dtrace/amd64/dtrace_subr.c b/sys/cddl/dev/dtrace/amd64/dtrace_subr.c
index f86f535..52da1b7 100644
--- a/sys/cddl/dev/dtrace/amd64/dtrace_subr.c
+++ b/sys/cddl/dev/dtrace/amd64/dtrace_subr.c
@@ -487,7 +487,7 @@ dtrace_trap(struct trapframe *frame, u_int type)
* A trap can occur while DTrace executes a probe. Before
* executing the probe, DTrace blocks re-scheduling and sets
* a flag in it's per-cpu flags to indicate that it doesn't
- * want to fault. On returning from the the probe, the no-fault
+ * want to fault. On returning from the probe, the no-fault
* flag is cleared and finally re-scheduling is enabled.
*
* Check if DTrace has enabled 'no-fault' mode:
diff --git a/sys/cddl/dev/dtrace/i386/dtrace_subr.c b/sys/cddl/dev/dtrace/i386/dtrace_subr.c
index be23808..c5ea277 100644
--- a/sys/cddl/dev/dtrace/i386/dtrace_subr.c
+++ b/sys/cddl/dev/dtrace/i386/dtrace_subr.c
@@ -487,7 +487,7 @@ dtrace_trap(struct trapframe *frame, u_int type)
* A trap can occur while DTrace executes a probe. Before
* executing the probe, DTrace blocks re-scheduling and sets
* a flag in it's per-cpu flags to indicate that it doesn't
- * want to fault. On returning from the the probe, the no-fault
+ * want to fault. On returning from the probe, the no-fault
* flag is cleared and finally re-scheduling is enabled.
*
* Check if DTrace has enabled 'no-fault' mode:
OpenPOWER on IntegriCloud