From: Petr Machata <petrm@nvidia.com>
To: Andrea Claudi <aclaudi@redhat.com>
Cc: <netdev@vger.kernel.org>, Leon Romanovsky <leon@kernel.org>,
Jiri Pirko <jiri@resnulli.us>, Jon Maloy <jmaloy@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH iproute2 2/2] treewide: fix typos in various comments
Date: Wed, 10 Jan 2024 11:54:51 +0100 [thread overview]
Message-ID: <87ply9o3lc.fsf@nvidia.com> (raw)
In-Reply-To: <f384c3720a340ca5302ee0f97d5e2127e246ce01.1704816744.git.aclaudi@redhat.com>
Andrea Claudi <aclaudi@redhat.com> writes:
> Fix various typos and spelling errors in some iproute2 comments.
>
> Signed-off-by: Andrea Claudi <aclaudi@redhat.com>
Reviewed-by: Petr Machata <petrm@nvidia.com>
> diff --git a/include/bpf_api.h b/include/bpf_api.h
> index 5887d3a8..287f96b6 100644
> --- a/include/bpf_api.h
> +++ b/include/bpf_api.h
> @@ -253,7 +253,7 @@ static int BPF_FUNC(skb_set_tunnel_opt, struct __sk_buff *skb,
> # define memmove(d, s, n) __builtin_memmove((d), (s), (n))
> #endif
>
> -/* FIXME: __builtin_memcmp() is not yet fully useable unless llvm bug
> +/* FIXME: __builtin_memcmp() is not yet fully usable unless llvm bug
> * https://llvm.org/bugs/show_bug.cgi?id=26218 gets resolved. Also
> * this one would generate a reloc entry (non-map), otherwise.
> */
BTW, I wouldn't spell it "useable" myself, but I think it is not
incorrect.
next prev parent reply other threads:[~2024-01-10 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 16:32 [PATCH iproute2 0/2] Fix some more typos in docs and comments Andrea Claudi
2024-01-09 16:32 ` [PATCH iproute2 1/2] docs, man: fix some typos Andrea Claudi
2024-01-10 10:35 ` Petr Machata
2024-01-11 17:21 ` Stephen Hemminger
2024-01-11 19:39 ` Stephen Hemminger
2024-01-09 16:32 ` [PATCH iproute2 2/2] treewide: fix typos in various comments Andrea Claudi
2024-01-10 10:54 ` Petr Machata [this message]
2024-01-11 19:40 ` Stephen Hemminger
2024-01-12 11:23 ` Andrea Claudi
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=87ply9o3lc.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=aclaudi@redhat.com \
--cc=dsahern@gmail.com \
--cc=jiri@resnulli.us \
--cc=jmaloy@redhat.com \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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;
as well as URLs for NNTP newsgroup(s).