From: patchwork-bot+netdevbpf@kernel.org
To: Jilin Yuan <yuanjilin@cdjrlc.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, idosch@nvidia.com, petrm@nvidia.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mellanox/mlxsw: fix repeated words in comments
Date: Fri, 01 Jul 2022 10:40:17 +0000 [thread overview]
Message-ID: <165667201756.26485.9541138901183243656.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220630074221.63148-1-yuanjilin@cdjrlc.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 30 Jun 2022 15:42:21 +0800 you wrote:
> Delete the redundant word 'action'.
> Delete the redundant word 'refer'.
> Delete the redundant word 'for'.
>
> Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
> ---
> drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_actions.c | 2 +-
> drivers/net/ethernet/mellanox/mlxsw/core_env.c | 2 +-
> drivers/net/ethernet/mellanox/mlxsw/spectrum2_kvdl.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
Here is the summary with links:
- mellanox/mlxsw: fix repeated words in comments
https://git.kernel.org/netdev/net-next/c/627838275a54
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-07-01 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 7:42 [PATCH] mellanox/mlxsw: fix repeated words in comments Jilin Yuan
2022-06-30 10:45 ` Ido Schimmel
2022-07-01 10:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-08 12:43 wangjianli
2022-09-08 13:57 ` Randy Dunlap
2022-09-16 10:50 ` 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=165667201756.26485.9541138901183243656.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=yuanjilin@cdjrlc.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.