From: Simon Horman <simon.horman@corigine.com>
To: Slark Xiao <slark_xiao@163.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
oss-drivers@corigine.com, netdev@vger.kernel.org
Subject: Re: [PATCH] nfp: bpf: Fix typo 'the the' in comment
Date: Fri, 22 Jul 2022 10:53:31 +0200 [thread overview]
Message-ID: <Ytpli3DNkg1HlJJ1@corigine.com> (raw)
In-Reply-To: <20220722082027.74046-1-slark_xiao@163.com>
On Fri, Jul 22, 2022 at 04:20:27PM +0800, Slark Xiao wrote:
> Replace 'the the' with 'the' in the comment.
>
> Signed-off-by: Slark Xiao <slark_xiao@163.com>
Thanks for noticing this and helping to improve the NFP driver.
Acked-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2022-07-22 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 8:20 [PATCH] nfp: bpf: Fix typo 'the the' in comment Slark Xiao
2022-07-22 8:53 ` Simon Horman [this message]
2022-07-25 10:10 ` 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=Ytpli3DNkg1HlJJ1@corigine.com \
--to=simon.horman@corigine.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=slark_xiao@163.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