From: patchwork-bot+netdevbpf@kernel.org
To: <Tristram.Ha@microchip.com>
Cc: linux@rempel-privat.de, m.grzeschik@pengutronix.de,
woojung.huh@microchip.com, andrew@lunn.ch, olteanv@gmail.com,
maxime.chevallier@bootlin.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, tristram.ha@microchip.com
Subject: Re: [PATCH net] net: dsa: microchip: Fix wrong rx drop MIB counter for KSZ8863
Date: Fri, 25 Jul 2025 22:17:26 +0000 [thread overview]
Message-ID: <175348184625.3265195.11254168994725323739.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250723030403.56878-1-Tristram.Ha@microchip.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Jul 2025 20:04:03 -0700 you wrote:
> From: Tristram Ha <tristram.ha@microchip.com>
>
> When KSZ8863 support was first added to KSZ driver the RX drop MIB
> counter was somehow defined as 0x105. The TX drop MIB counter
> starts at 0x100 for port 1, 0x101 for port 2, and 0x102 for port 3, so
> the RX drop MIB counter should start at 0x103 for port 1, 0x104 for
> port 2, and 0x105 for port 3.
>
> [...]
Here is the summary with links:
- [net] net: dsa: microchip: Fix wrong rx drop MIB counter for KSZ8863
https://git.kernel.org/netdev/net/c/165a7f5db919
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:[~2025-07-25 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 3:04 Tristram.Ha
2025-07-23 4:59 ` Oleksij Rempel
2025-07-25 22:17 ` 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=175348184625.3265195.11254168994725323739.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=m.grzeschik@pengutronix.de \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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®