[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241210185321.23144-1-pvkumar5749404@gmail.com>
Date: Wed, 11 Dec 2024 00:23:21 +0530
From: Prabhav Kumar Vaish <pvkumar5749404@...il.com>
To: ast@...nel.org,
daniel@...earbox.net,
andrii@...nel.org,
martin.lau@...ux.dev,
eddyz87@...il.com,
song@...nel.org,
yonghong.song@...ux.dev,
john.fastabend@...il.com,
kpsingh@...nel.org,
sdf@...ichev.me,
haoluo@...gle.com,
jolsa@...nel.org
Cc: Prabhav Kumar Vaish <pvkumar5749404@...il.com>,
bpf@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH bpf-next] BPF-Helpers : Correct spelling mistake
Changes :
- "unsinged" is spelled correctly to "unsigned"
Signed-off-by: Prabhav Kumar Vaish <pvkumar5749404@...il.com>
---
kernel/bpf/helpers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/bpf/helpers.c b/kernel/bpf/helpers.c
index 532ea74d4850..1493f1daecaa 100644
--- a/kernel/bpf/helpers.c
+++ b/kernel/bpf/helpers.c
@@ -3057,7 +3057,7 @@ __bpf_kfunc int bpf_copy_from_user_str(void *dst, u32 dst__sz, const void __user
return ret + 1;
}
-/* Keep unsinged long in prototype so that kfunc is usable when emitted to
+/* Keep unsigned long in prototype so that kfunc is usable when emitted to
* vmlinux.h in BPF programs directly, but note that while in BPF prog, the
* unsigned long always points to 8-byte region on stack, the kernel may only
* read and write the 4-bytes on 32-bit.
--
2.34.1
Powered by blists - more mailing lists