Received-SPF: pass (google.com: domain of linux-kernel+bounces-178663-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net] net: micrel: Fix receiving the timestamp in the frame for
 lan8841
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <171569042875.21890.7113805948748540771.git-patchwork-notify@kernel.org>
Date: Tue, 14 May 2024 12:40:28 +0000
References: <20240513192157.3917664-1-horatiu.vultur@microchip.com>
In-Reply-To: <20240513192157.3917664-1-horatiu.vultur@microchip.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
 davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
 richardcochran@gmail.com, netdev@vger.kernel.org,
 linux-kernel@vger.kernel.org

Hello:

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

On Mon, 13 May 2024 21:21:57 +0200 you wrote:
> The blamed commit started to use the ptp workqueue to get the second
> part of the timestamp. And when the port was set down, then this
> workqueue is stopped. But if the config option NETWORK_PHY_TIMESTAMPING
> is not enabled, then the ptp_clock is not initialized so then it would
> crash when it would try to access the delayed work.
> So then basically by setting up and then down the port, it would crash.
> The fix consists in checking if the ptp_clock is initialized and only
> then cancel the delayed work.
> 
> [...]

Here is the summary with links:
  - [net] net: micrel: Fix receiving the timestamp in the frame for lan8841
    https://git.kernel.org/netdev/net/c/aea27a92a41d

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