Re: [PATCH 6/7] tools/lib: fix typos in comments

[bot+bpf-ci]

> diff --git a/tools/lib/bpf/btf.c b/tools/lib/bpf/btf.c
> index 8417de92d0282..c1745bee37c0a 100644
> --- a/tools/lib/bpf/btf.c
> +++ b/tools/lib/bpf/btf.c
> @@ -3843,7 +3843,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`
> @@ -5644,7 +5644,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 2e56e3ab5b6cc..c0933580930bc 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

This isn't a bug, but both files here are under tools/lib/bpf/, where recent
commits use the 'libbpf: Fix ...' subject form - would 'libbpf: Fix typos in
comments' fit the tree's convention better?


---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md

CI run summary: https://github.com/kernel-patches/bpf/actions/runs/33866776554