From: Ankan Biswas <spyjetfayed@gmail.com>
To: Martin KaFai Lau <martin.lau@linux.dev>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] docs: bpf: fix minor typos in BTF comments
Date: Fri, 1 Aug 2025 18:59:23 +0530 [thread overview]
Message-ID: <c08c2cb8-4760-4b21-9beb-2e9c204a62dc@gmail.com> (raw)
From 85f5a63a12a8544440c0af47214ba5f55c348c7c Mon Sep 17 00:00:00 2001
From: Ankan Biswas <spyjetfayed@gmail.com>
Date: Fri, 1 Aug 2025 18:25:21 +0530
Subject: [PATCH] docs: bpf: fix minor typos in BTF comments
Fix a couple of small typos in the BTF documentation comments:
* "focus" → "focuses"
* "F.e." → "For example,"
Signed-off-by: Ankan Biswas <spyjetfayed@gmail.com>
---
kernel/bpf/btf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
index 64739308902f..a0ecf162918c 100644
--- a/kernel/bpf/btf.c
+++ b/kernel/bpf/btf.c
@@ -35,7 +35,7 @@
#include "../tools/lib/bpf/relo_core.h"
/* BTF (BPF Type Format) is the meta data format which describes
- * the data types of BPF program/map. Hence, it basically focus
+ * the data types of BPF program/map. Hence, it basically focuses
* on the C programming language which the modern BPF is primary
* using.
*
@@ -47,7 +47,7 @@
* ~~~~~~~~~~~~~~~
* Each 'struct btf_type' object describes a C data type.
* Depending on the type it is describing, a 'struct btf_type'
- * object may be followed by more data. F.e.
+ * object may be followed by more data. For example,
* To describe an array, 'struct btf_type' is followed by
* 'struct btf_array'.
*
--
2.50.1
next reply other threads:[~2025-08-01 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 13:29 Ankan Biswas [this message]
2025-08-01 16:39 ` [PATCH] docs: bpf: fix minor typos in BTF comments Yonghong Song
2025-08-01 17:01 ` Ankan Biswas
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=c08c2cb8-4760-4b21-9beb-2e9c204a62dc@gmail.com \
--to=spyjetfayed@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
/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