From patchwork Tue Nov 23 15:44:01 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: =?utf-8?q?Marek_Beh=C3=BAn?= X-Patchwork-Id: 12634515 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89C70C433F5 for ; Tue, 23 Nov 2021 15:44:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236175AbhKWPrQ (ORCPT ); Tue, 23 Nov 2021 10:47:16 -0500 Received: from mail.kernel.org ([198.145.29.99]:34852 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236148AbhKWPrQ (ORCPT ); Tue, 23 Nov 2021 10:47:16 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4560260E54; Tue, 23 Nov 2021 15:44:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1637682248; bh=tp/slqvdmPi2FebVHoL4t4VkbO2brAsEfdU464cgMlw=; h=From:To:Cc:Subject:Date:From; b=fcQzjH4EhAgghdCq1uo/iCEbXWabSq1V8a5GYhH+rcQnopxqiN1fKLiUuwFCCtUaM dmPhchiDI1+4tXLCJPFFbDQeDUCBPJqOKd7gC0Kz35c4esCIIcdKA/pAjM+bzqNe6V Xl3kJUVMK2zuTTYw1UYMkiinLPULSCf7QzUV223qf7x+ycHw1+NsElZqbTBAYfFCNj xR2EJPHsZJ+B5qZt3NUlF8GkZ391S4YktLS/APmykST3Q+Am5aBYe7M3JOdZ6KPwC2 WAI0KLPLyehUHHD2TcXkW/eZld1gvqrgo3Iz0I/51rE0L/YqvRs2fz1zOEtPZYCsQs /WLWwKNEuHJcg== From: =?utf-8?q?Marek_Beh=C3=BAn?= To: netdev@vger.kernel.org Cc: Russell King , Jakub Kicinski , Andrew Lunn , davem@davemloft.net, =?utf-8?q?Marek_Beh=C3=BAn?= Subject: [PATCH net v2 0/2] phylink resolve fixes Date: Tue, 23 Nov 2021 16:44:01 +0100 Message-Id: <20211123154403.32051-1-kabel@kernel.org> X-Mailer: git-send-email 2.32.0 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org With information from me and my nagging, Russell has produced two fixes for phylink, which add code that triggers another phylink_resolve() from phylink_resolve(), if certain conditions are met: interface is being changed or link is down and previous link was up These are needed because sometimes the PCS callbacks may provide stale values if link / speed / ... Changes from v1: - set Russell as author of the commits, since I only wrote the commit messages - updated the second patch according to Russell's comment (and updated commit message) Russell King (Oracle) (2): net: phylink: Force link down and retrigger resolve on interface change net: phylink: Force retrigger in case of latched link-fail indicator drivers/net/phy/phylink.c | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-)