From: Greg KH <gregkh@linuxfoundation.org>
To: Taichi Nishimura <awkrail01@gmail.com>
Cc: andrii@kernel.org, mykolal@fb.com, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
shuah@kernel.org, davem@davemloft.net, kuba@kernel.org,
hawk@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
trix@redhat.com, iii@linux.ibm.com, ytcoode@gmail.com,
deso@posteo.net, memxor@gmail.com, joannelkoong@gmail.com,
rdunlap@infradead.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH bpf-next] Fix typos in selftest/bpf files
Date: Thu, 16 Feb 2023 09:16:10 +0100 [thread overview]
Message-ID: <Y+3mSp2j2Xqe1sT0@kroah.com> (raw)
In-Reply-To: <20230216080423.513746-1-awkrail01@gmail.com>
On Thu, Feb 16, 2023 at 05:04:23PM +0900, Taichi Nishimura wrote:
> This patch is a re-submitting patch.
> I cloned bpf-next repo, run spell checker, and fixed typos.
> Included v1 and v2 patches to this one.
>
> Could you review it again?
> Let me know if I have any mistakes.
This text is not needed in the changelog for a patch, please read the
section entitled "The canonical patch format" in the kernel file,
Documentation/process/submitting-patches.rst for what is needed in order
to properly describe the change.
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-16 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 8:04 [PATCH bpf-next] Fix typos in selftest/bpf files Taichi Nishimura
2023-02-16 8:16 ` Greg KH [this message]
2023-02-16 8:30 ` Randy Dunlap
2023-02-16 14:51 ` [Re: PATCH " Taichi Nishimura
-- strict thread matches above, loose matches on Subject: below --
2023-02-16 8:55 [PATCH " Taichi Nishimura
2023-02-16 16:58 ` Randy Dunlap
2023-02-17 1:00 ` 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=Y+3mSp2j2Xqe1sT0@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=awkrail01@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=deso@posteo.net \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=iii@linux.ibm.com \
--cc=joannelkoong@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mykolal@fb.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=trix@redhat.com \
--cc=yhs@fb.com \
--cc=ytcoode@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.