From: Randy Dunlap <rdunlap@infradead.org>
To: Song Liu <song@kernel.org>, trix@redhat.com
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bpf: cleanup comments
Date: Sun, 20 Feb 2022 17:29:58 -0800 [thread overview]
Message-ID: <a7c2bc3c-16e6-735f-4bc8-b57a48daec7d@infradead.org> (raw)
In-Reply-To: <CAPhsuW7j9SK5OJxK-ZnDYgwVhoPJGP8K+1Q+pUJ8mGUA41ZvHQ@mail.gmail.com>
On 2/20/22 17:28, Song Liu wrote:
> On Sun, Feb 20, 2022 at 10:41 AM <trix@redhat.com> wrote:
>>
>> From: Tom Rix <trix@redhat.com>
>>
>> Add leading space to spdx tag
>> Use // for spdx c file comment
>>
>> Replacements
>> resereved to reserved
>> inbetween to in between
>> everytime to every time
>
> I think everytime could be a single word? Other than that,
Nope. :)
>
> Acked-by: Song Liu <songliubraving@fb.com>
>
>> intutivie to intuitive
>> currenct to current
>> encontered to encountered
>> referenceing to referencing
>> upto to up to
>> exectuted to executed
>>
>> Signed-off-by: Tom Rix <trix@redhat.com>
>> ---
>> kernel/bpf/bpf_local_storage.c | 2 +-
>> kernel/bpf/btf.c | 6 +++---
>> kernel/bpf/cgroup.c | 8 ++++----
>> kernel/bpf/hashtab.c | 2 +-
>> kernel/bpf/helpers.c | 2 +-
>> kernel/bpf/local_storage.c | 2 +-
>> kernel/bpf/reuseport_array.c | 2 +-
>> kernel/bpf/syscall.c | 2 +-
>> kernel/bpf/trampoline.c | 2 +-
>> 9 files changed, 14 insertions(+), 14 deletions(-)
--
~Randy
next prev parent reply other threads:[~2022-02-21 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 18:40 trix
2022-02-21 1:28 ` Song Liu
2022-02-21 1:29 ` Randy Dunlap [this message]
2022-02-21 10:02 ` Nicolas Dichtel
2022-02-23 23:20 ` 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=a7c2bc3c-16e6-735f-4bc8-b57a48daec7d@infradead.org \
--to=rdunlap@infradead.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=song@kernel.org \
--cc=songliubraving@fb.com \
--cc=trix@redhat.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
all inboxes | Powered by JetHome®