From: patchwork-bot+netdevbpf@kernel.org
To: Jeffrey Ji <jeffreyjilinux@gmail.com>
Cc: brianvv@google.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
edumazet@google.com, bigeasy@linutronix.de, toke@redhat.com,
imagedong@tencent.com, petrm@nvidia.com, memxor@gmail.com,
arnd@arndb.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jeffreyji@google.com
Subject: Re: [PATCH net-next] net-core: rx_otherhost_dropped to core_stats
Date: Fri, 08 Apr 2022 04:00:13 +0000 [thread overview]
Message-ID: <164939041350.25172.4449990089641663933.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220406172600.1141083-1-jeffreyjilinux@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 Apr 2022 17:26:00 +0000 you wrote:
> From: Jeffrey Ji <jeffreyji@google.com>
>
> Increment rx_otherhost_dropped counter when packet dropped due to
> mismatched dest MAC addr.
>
> An example when this drop can occur is when manually crafting raw
> packets that will be consumed by a user space application via a tap
> device. For testing purposes local traffic was generated using trafgen
> for the client and netcat to start a server
>
> [...]
Here is the summary with links:
- [net-next] net-core: rx_otherhost_dropped to core_stats
https://git.kernel.org/netdev/net-next/c/794c24e9921f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-08 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 17:26 [PATCH net-next] net-core: rx_otherhost_dropped to core_stats Jeffrey Ji
2022-04-07 5:31 ` Jakub Kicinski
2022-04-07 15:36 ` Brian Vazquez
2022-04-07 15:39 ` Eric Dumazet
2022-04-08 4:00 ` patchwork-bot+netdevbpf [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=164939041350.25172.4449990089641663933.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=jeffreyji@google.com \
--cc=jeffreyjilinux@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=toke@redhat.com \
--cc=yoshfuji@linux-ipv6.org \
/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