[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200623084207.149253-1-colin.king@canonical.com>
Date: Tue, 23 Jun 2020 09:42:07 +0100
From: Colin King <colin.king@...onical.com>
To: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
Andrii Nakryiko <andriin@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...omium.org>, netdev@...r.kernel.org,
bpf@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH][next] libbpf: fix spelling mistake "kallasyms" -> "kallsyms"
From: Colin Ian King <colin.king@...onical.com>
There is a spelling mistake in a pr_warn message. Fix it.
Signed-off-by: Colin Ian King <colin.king@...onical.com>
---
tools/lib/bpf/libbpf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index 18461deb1b19..deea27aadcef 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -5741,7 +5741,7 @@ static int bpf_object__read_kallsyms_file(struct bpf_object *obj)
if (ret == EOF && feof(f))
break;
if (ret != 3) {
- pr_warn("failed to read kallasyms entry: %d\n", ret);
+ pr_warn("failed to read kallsyms entry: %d\n", ret);
err = -EINVAL;
goto out;
}
--
2.27.0
Powered by blists - more mailing lists