From: John Fastabend <john.fastabend@gmail.com>
To: menglong8.dong@gmail.com, kuba@kernel.org
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
andrii@kernel.org, john.fastabend@gmail.com,
kpsingh@chromium.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
Menglong Dong <dong.menglong@zte.com.cn>
Subject: RE: [PATCH] net: sched: fix misspellings using misspell-fixer tool
Date: Mon, 09 Nov 2020 13:23:27 -0800 [thread overview]
Message-ID: <5fa9b34f132a5_8c0e208ca@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <5fa8e9d4.1c69fb81.5d889.5c64@mx.google.com>
menglong8.dong@ wrote:
> From: Menglong Dong <dong.menglong@zte.com.cn>
>
> Some typos are found out by misspell-fixer tool:
>
> $ misspell-fixer -rnv ./net/sched/
> ./net/sched/act_api.c:686
> ./net/sched/act_bpf.c:68
> ./net/sched/cls_rsvp.h:241
> ./net/sched/em_cmp.c:44
> ./net/sched/sch_pie.c:408
>
> Fix typos found by misspell-fixer.
>
> Signed-off-by: Menglong Dong <dong.menglong@zte.com.cn>
> ---
Hi, you will want to add net-next to the [PATCH *] line next time
to make it clear this is for net-next. The contents make it
obvious in this case though.
Also I'm not sure why the bpf@ include but OK.
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2020-11-09 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 7:02 [PATCH] net: sched: fix misspellings using misspell-fixer tool menglong8.dong
2020-11-09 21:23 ` John Fastabend [this message]
2020-11-10 15:36 ` Menglong Dong
2020-11-11 1:00 ` Jakub Kicinski
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=5fa9b34f132a5_8c0e208ca@john-XPS-13-9370.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dong.menglong@zte.com.cn \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=xiyou.wangcong@gmail.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