netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heng Guo <heng.guo@windriver.com>
Cc: davem@davemloft.net, sahern@kernel.org, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	Richard.Danter@windriver.com, filip.pudak@windriver.com
Subject: Re: [PATCH 0/1] Issue description and debug
Date: Wed, 30 Aug 2023 08:50:22 +0000	[thread overview]
Message-ID: <169338542205.27846.810600135070334068.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230825075505.3932972-1-heng.guo@windriver.com>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Fri, 25 Aug 2023 15:55:04 +0800 you wrote:
> Hi maintainers,
> 
> The IPSTATS_MIB_OUTOCTETS increment is duplicated in SNMP test.
> 
> Reproduce environment:
> network with 3 VM linuxs is connected as below:
> VM1<---->VM2(latest kernel 6.5.0-rc7)<---->VM3
> VM1: eth0 ip: 192.168.122.207
> VM2: eth0 ip: 192.168.122.208, eth1 ip: 192.168.123.104
> VM3: eth0 ip: 192.168.123.240
> 
> [...]

Here is the summary with links:
  - [1/1] net: ipv4, ipv6: fix IPSTATS_MIB_OUTOCTETS increment duplicated
    https://git.kernel.org/netdev/net/c/e4da8c78973c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-08-30  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  7:55 [PATCH 0/1] Issue description and debug Heng Guo
2023-08-25  7:55 ` [PATCH 1/1] net: ipv4, ipv6: fix IPSTATS_MIB_OUTOCTETS increment duplicated Heng Guo
2023-08-30  8:50 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-14  5:16 [PATCH 0/1] Issue description and debug Heng Guo
2023-10-08  0:59 Heng Guo

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=169338542205.27846.810600135070334068.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Richard.Danter@windriver.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=filip.pudak@windriver.com \
    --cc=heng.guo@windriver.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sahern@kernel.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;
as well as URLs for NNTP newsgroup(s).