From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8F434C2D0BF for ; Tue, 10 Dec 2019 21:15:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5926F2077B for ; Tue, 10 Dec 2019 21:15:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576012500; bh=J0TK57Std5KN5JvAxyqjEri5SWz6RNnh3aD40avj88M=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=E1U/7alirg1iZWDabxwqVUdeoIo4tGaUyGKLCOB1PVAGGOAZICxm0HXTmgEG3zxHB owdmosmzuzwpwY1tz2AbxbzT8k81BWUpxd0V5Z7NDMyXe/mcs0vN2btG8rvez/2ciN 586YH1lrxfPPcNW0lj93GVqt1bdL3MLmcaCe3j94= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726860AbfLJVOu (ORCPT ); Tue, 10 Dec 2019 16:14:50 -0500 Received: from mail.kernel.org ([198.145.29.99]:40658 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729446AbfLJVNs (ORCPT ); Tue, 10 Dec 2019 16:13:48 -0500 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9A9CE24655; Tue, 10 Dec 2019 21:13:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576012428; bh=J0TK57Std5KN5JvAxyqjEri5SWz6RNnh3aD40avj88M=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=j8O1QESCTY1clt24hEI7YMct68IUpjDLS73W3kpx1tXGxs7UC9GIwBEi0YR6cznF9 IsazUufcIqAeje557c7EpcfDBbLzwm2+cxoz2FMURuME9ShZTn03pcJhMOMj+YT9wL hzUNxW5+k8gi9flSk1q0N0xVsWufes4/6VWS2mis= From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Russell King , Jakub Kicinski , Sasha Levin , netdev@vger.kernel.org Subject: [PATCH AUTOSEL 5.4 342/350] net: phy: initialise phydev speed and duplex sanely Date: Tue, 10 Dec 2019 16:07:27 -0500 Message-Id: <20191210210735.9077-303-sashal@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20191210210735.9077-1-sashal@kernel.org> References: <20191210210735.9077-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org From: Russell King [ Upstream commit a5d66f810061e2dd70fb7a108dcd14e535bc639f ] When a phydev is created, the speed and duplex are set to zero and -1 respectively, rather than using the predefined SPEED_UNKNOWN and DUPLEX_UNKNOWN constants. There is a window at initialisation time where we may report link down using the 0/-1 values. Tidy this up and use the predefined constants, so debug doesn't complain with: "Unsupported (update phy-core.c)/Unsupported (update phy-core.c)" when the speed and duplex settings are printed. Signed-off-by: Russell King Signed-off-by: Jakub Kicinski Signed-off-by: Sasha Levin --- drivers/net/phy/phy_device.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c index 14c6b7597b06e..cee8724caf2d7 100644 --- a/drivers/net/phy/phy_device.c +++ b/drivers/net/phy/phy_device.c @@ -596,8 +596,8 @@ struct phy_device *phy_device_create(struct mii_bus *bus, int addr, int phy_id, mdiodev->device_free = phy_mdio_device_free; mdiodev->device_remove = phy_mdio_device_remove; - dev->speed = 0; - dev->duplex = -1; + dev->speed = SPEED_UNKNOWN; + dev->duplex = DUPLEX_UNKNOWN; dev->pause = 0; dev->asym_pause = 0; dev->link = 0; -- 2.20.1