From: Martin Lau <kafai@fb.com>
To: Colin King <colin.king@canonical.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] bpf: hbm: fix spelling mistake "notifcations" -> "notificiations"
Date: Mon, 3 Jun 2019 17:42:51 +0000 [thread overview]
Message-ID: <20190603174234.5cixc57p64aqm7om@kafai-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20190603133653.18185-1-colin.king@canonical.com>
On Mon, Jun 03, 2019 at 02:36:53PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in the help information, fix this.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> samples/bpf/hbm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/samples/bpf/hbm.c b/samples/bpf/hbm.c
> index 480b7ad6a1f2..bdfce592207a 100644
> --- a/samples/bpf/hbm.c
> +++ b/samples/bpf/hbm.c
> @@ -411,7 +411,7 @@ static void Usage(void)
> " -l also limit flows using loopback\n"
> " -n <#> to create cgroup \"/hbm#\" and attach prog\n"
> " Default is /hbm1\n"
> - " --no_cn disable CN notifcations\n"
> + " --no_cn disable CN notifications\n"
Acked-by: Martin KaFai Lau <kafai@fb.com>
This should go to the bpf-next.
next prev parent reply other threads:[~2019-06-03 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 13:36 [PATCH][next] bpf: hbm: fix spelling mistake "notifcations" -> "notificiations" Colin King
2019-06-03 17:42 ` Martin Lau [this message]
2019-06-04 15:04 ` Daniel Borkmann
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=20190603174234.5cixc57p64aqm7om@kafai-mbp.dhcp.thefacebook.com \
--to=kafai@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.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 \
--cc=songliubraving@fb.com \
--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;
as well as URLs for NNTP newsgroup(s).