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-next] net: dsa: microchip: Do not execute PTP driver code for unsupported switches
Date: Fri, 20 Dec 2024 21:50:29 +0000 [thread overview]
Message-ID: <173473142901.3030742.8395151277064990661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241218020240.70601-1-Tristram.Ha@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Dec 2024 18:02:40 -0800 you wrote:
> From: Tristram Ha <tristram.ha@microchip.com>
>
> The PTP driver code only works for certain KSZ switches like KSZ9477,
> KSZ9567, LAN937X and their varieties. This code is enabled by kernel
> configuration CONFIG_NET_DSA_MICROCHIP_KSZ_PTP. As the DSA driver is
> common to work with all KSZ switches this PTP code is not appropriate
> for other unsupported switches. The ptp_capable indication is added to
> the chip data structure to signal whether to execute those code.
>
> [...]
Here is the summary with links:
- [net-next] net: dsa: microchip: Do not execute PTP driver code for unsupported switches
https://git.kernel.org/netdev/net-next/c/6ed3472173c5
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 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 2:02 [PATCH net-next] net: dsa: microchip: Do not execute PTP driver code for unsupported switches Tristram.Ha
2024-12-20 21:50 ` 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=173473142901.3030742.8395151277064990661.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.