mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, olteanv@gmail.com,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: motorcomm: Free the MIB block on port teardown
Date: Wed, 11 Nov 2026 23:20:05 +0000	[thread overview]
Message-ID: <179443920518.1699546.17528295651329739725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109144705.1737460-1-mmyangfl@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon,  9 Nov 2026 22:46:50 +0800 you wrote:
> .setup() can run again within one registration: removing another switch
> from the tree tears the whole tree down, and re-probing sets every
> member switch up again.
> 
> The hardware reset at the start of .setup() brings the MIB counters back
> to zero, but a MIB block kept across that cycle still holds the old
> software buffer, so the next yt921x_mib_read() treats the small value as
> a 32-bit wrap and adds 2^32 to every counter it extends.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: dsa: motorcomm: Free the MIB block on port teardown
    https://git.kernel.org/netdev/net-next/c/a9a173f81c83

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



      parent reply	other threads:[~2026-11-11 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 14:46 David Yang
2026-11-09 14:51 ` netdev-bot+sinfo
2026-11-09 14:52   ` David Yang
2026-11-11 23:20 ` 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=179443920518.1699546.17528295651329739725.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmyangfl@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.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
all inboxes | Powered by JetHome®