From: Taichi Nishimura <awkrail01@gmail.com>
To: rdunlap@infradead.org
Cc: andrii@kernel.org, ast@kernel.org, awkrail01@gmail.com,
bpf@vger.kernel.org, daniel@iogearbox.net, davem@davemloft.net,
deso@posteo.net, haoluo@google.com, hawk@kernel.org,
iii@linux.ibm.com, joannelkoong@gmail.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, llvm@lists.linux.dev,
martin.lau@linux.dev, memxor@gmail.com, mykolal@fb.com,
nathan@kernel.org, ndesaulniers@google.com,
netdev@vger.kernel.org, sdf@google.com, shuah@kernel.org,
song@kernel.org, trix@redhat.com, yhs@fb.com, ytcoode@gmail.com,
gregkh@linuxfoundation.org
Subject: [Re: PATCH bpf-next] Fix typos in selftest/bpf files
Date: Thu, 16 Feb 2023 23:51:45 +0900 [thread overview]
Message-ID: <20230216145145.548183-1-awkrail01@gmail.com> (raw)
In-Reply-To: <4753a724-2fd4-3672-c7ce-0164fe759eea@infradead.org>
> 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
> Hi,
> The corrections all look good.
> Of course, you need to fix what Greg mentioned, then you can resubmit
> the patch with this added:
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Thanks.
Thank you for your reviewing and advices.
I am a beginner so they are helpful.
I read the docs and re-sent a patch.
After sending it, I found forgetting to reply to this thread...
Sorry in advance.
prev parent reply other threads:[~2023-02-16 14:52 UTC|newest]
Thread overview: 4+ 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
2023-02-16 8:30 ` Randy Dunlap
2023-02-16 14:51 ` Taichi Nishimura [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=20230216145145.548183-1-awkrail01@gmail.com \
--to=awkrail01@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=deso@posteo.net \
--cc=gregkh@linuxfoundation.org \
--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 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).