From: patchwork-bot+netdevbpf@kernel.org
To: <Tristram.Ha@microchip.com>
Cc: woojung.huh@microchip.com, arun.ramadoss@microchip.com,
andrew@lunn.ch, olteanv@gmail.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 0/2] net: dsa: microchip: Fix set_ageing_time function for KSZ9477 and LAN937X switches
Date: Fri, 20 Dec 2024 02:10:32 +0000 [thread overview]
Message-ID: <173466063251.2449610.12849962822761975977.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241218020224.70590-1-Tristram.Ha@microchip.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Dec 2024 18:02:22 -0800 you wrote:
> From: Tristram Ha <tristram.ha@microchip.com>
>
> The aging count is not a simple number that is broken into two parts and
> programmed into 2 registers. These patches correct the programming for
> KSZ9477 and LAN937X switches.
>
> Tristram Ha (2):
> net: dsa: microchip: Fix KSZ9477 set_ageing_time function
> net: dsa: microchip: Fix LAN937X set_ageing_time function
>
> [...]
Here is the summary with links:
- [net,1/2] net: dsa: microchip: Fix KSZ9477 set_ageing_time function
https://git.kernel.org/netdev/net/c/262bfba8ab82
- [net,2/2] net: dsa: microchip: Fix LAN937X set_ageing_time function
https://git.kernel.org/netdev/net/c/bb9869043438
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:[~2024-12-20 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 2:02 Tristram.Ha
2024-12-18 2:02 ` [PATCH net 1/2] net: dsa: microchip: Fix KSZ9477 set_ageing_time function Tristram.Ha
2024-12-19 16:50 ` Andrew Lunn
2024-12-18 2:02 ` [PATCH net 2/2] net: dsa: microchip: Fix LAN937X " Tristram.Ha
2024-12-19 16:58 ` Andrew Lunn
2024-12-20 2:10 ` 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=173466063251.2449610.12849962822761975977.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=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®