From: Quentin Monnet <quentin@isovalent.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] bpftool: Fix spelling mistake "disasembler" -> "disassembler"
Date: Wed, 26 Oct 2022 11:47:31 +0100 [thread overview]
Message-ID: <e3b415c2-351f-e2df-4a24-6fa33df7d69b@isovalent.com> (raw)
In-Reply-To: <20221026081645.3186878-1-colin.i.king@gmail.com>
2022-10-26 09:16 UTC+0100 ~ Colin Ian King <colin.i.king@gmail.com>
> There is a spelling mistake in an error message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> tools/bpf/bpftool/jit_disasm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/bpf/bpftool/jit_disasm.c b/tools/bpf/bpftool/jit_disasm.c
> index 58a5017034a2..7b8d9ec89ebd 100644
> --- a/tools/bpf/bpftool/jit_disasm.c
> +++ b/tools/bpf/bpftool/jit_disasm.c
> @@ -223,7 +223,7 @@ static int init_context(disasm_ctx_t *ctx, const char *arch,
>
> memset(tpath, 0, sizeof(tpath));
> if (get_exec_path(tpath, sizeof(tpath))) {
> - p_err("failed to create disasembler (get_exec_path)");
> + p_err("failed to create disassembler (get_exec_path)");
> return -1;
> }
>
Thanks for the fix!
Acked-by: Quentin Monnet <quentin@isovalent.com>
next prev parent reply other threads:[~2022-10-26 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 8:16 [PATCH][next] bpftool: Fix spelling mistake "disasembler" -> "disassembler" Colin Ian King
2022-10-26 10:47 ` Quentin Monnet [this message]
2022-10-27 1:30 ` patchwork-bot+netdevbpf
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=e3b415c2-351f-e2df-4a24-6fa33df7d69b@isovalent.com \
--to=quentin@isovalent.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=colin.i.king@gmail.com \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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