[PATCH bpf-next v3 6/7] libbpf: Fix typos in comments
From: Hemanth Selam <hidden>
Date: 2026-09-07 12:01:54
Also in:
bpf, linux-arm-kernel, linux-kselftest, lkml, sparclinux
Subsystem:
bpf [general] (safe dynamic programs and tools), bpf [library] (libbpf), the rest · Maintainers:
Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko, Eduard Zingerman, Kumar Kartikeya Dwivedi, Linus Torvalds
Fix typos in comments, reported by scripts/checkpatch.pl using the misspelling list in scripts/spelling.txt. Only touches comments, no code changes. The subject changed since v1, from "tools/lib: fix typos in comments": both files are under tools/lib/bpf/, where the prevailing form is "libbpf: Fix ...". Assisted-by: Cursor:claude-opus-5 Signed-off-by: Hemanth Selam <redacted> --- tools/lib/bpf/btf.c | 4 ++-- tools/lib/bpf/usdt.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/lib/bpf/btf.c b/tools/lib/bpf/btf.c
index c783359977b4..d1c73113e58f 100644
--- a/tools/lib/bpf/btf.c
+++ b/tools/lib/bpf/btf.c@@ -3847,7 +3847,7 @@ static int btf_dedup_remap_types(struct btf_dedup *d); * types, in general, can form graphs containing cycles, not just DAGs. * * While algorithm does deduplication, it also merges and resolves type - * information (unless disabled throught `struct btf_opts`), whenever possible. + * information (unless disabled through `struct btf_opts`), whenever possible. * E.g., in the example above with two compilation units having partial type * information for structs `A` and `B`, the output of algorithm will emit * a single copy of each BTF type that describes structs `A`, `B`, and `S`
@@ -5648,7 +5648,7 @@ static int btf_dedup_resolve_fwds(struct btf_dedup *d) * * After we established for each type its corresponding canonical representative * type, we now can eliminate types that are not canonical and leave only - * canonical ones layed out sequentially in memory by copying them over + * canonical ones laid out sequentially in memory by copying them over * duplicates. During compaction btf_dedup->hypot_map array is reused to store * a map from original type ID to a new compacted type ID, which will be used * during next phase to "fix up" type IDs, referenced from struct/union and
diff --git a/tools/lib/bpf/usdt.c b/tools/lib/bpf/usdt.c
index ee9d1b614883..67c60f716c1a 100644
--- a/tools/lib/bpf/usdt.c
+++ b/tools/lib/bpf/usdt.c@@ -144,7 +144,7 @@ * about. This state has to be maintained per-BPF object and coordinate * between different USDT attachments within the same BPF object. * - * Spec ID is the key in spec BPF map, value is the actual USDT spec layed out + * Spec ID is the key in spec BPF map, value is the actual USDT spec laid out * as struct usdt_spec. Each invocation of BPF program at runtime needs to * know its associated spec ID. It gets it either through BPF cookie, which * libbpf sets to spec ID during attach time, or, if kernel is too old to
--
2.48.1