From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Colin King <colin.king@canonical.com>,
Alexei Starovoitov <ast@kernel.org>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][bpf-next] bpf: fix spelling mistake: "obusing" -> "abusing"
Date: Wed, 10 Jan 2018 14:56:04 -0800 [thread overview]
Message-ID: <20180110225602.synp2j4icjfife4x@ast-mbp> (raw)
In-Reply-To: <753b49bf-57e3-a559-6275-880cca2d426d@iogearbox.net>
On Wed, Jan 10, 2018 at 11:39:14AM +0100, Daniel Borkmann wrote:
> On 01/10/2018 10:20 AM, Colin King wrote:
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > Trivial fix to spelling mistake in error message text.
> >
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > ---
> > kernel/bpf/verifier.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> > index 97bbef3eecdf..e388f30c4168 100644
> > --- a/kernel/bpf/verifier.c
> > +++ b/kernel/bpf/verifier.c
> > @@ -5336,7 +5336,7 @@ static int fixup_bpf_calls(struct bpf_verifier_env *env)
> > */
> > map_ptr = env->insn_aux_data[i + delta].map_ptr;
> > if (map_ptr == BPF_MAP_PTR_POISON) {
> > - verbose(env, "tail_call obusing map_ptr\n");
> > + verbose(env, "tail_call abusing map_ptr\n");
> > return -EINVAL;
> > }
> > if (!map_ptr->unpriv_array)
> >
>
> This is not in bpf-next tree yet, but only in bpf tree. I will let this sit
> for a bit in patchwork until bpf-next has all the stuff from bpf merged back,
> and then apply it into bpf-next.
since the typo was just introduced in bpf tree it's better to fix it right away.
Applied, Thanks Colin.
prev parent reply other threads:[~2018-01-10 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 9:20 [PATCH][bpf-next] bpf: fix spelling mistake: "obusing" -> "abusing" Colin King
2018-01-10 10:39 ` Daniel Borkmann
2018-01-10 22:56 ` Alexei Starovoitov [this message]
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=20180110225602.synp2j4icjfife4x@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=colin.king@canonical.com \
--cc=daniel@iogearbox.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).