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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5AD86C4321E for ; Wed, 30 Nov 2022 19:43:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229678AbiK3Tns (ORCPT ); Wed, 30 Nov 2022 14:43:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54410 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229759AbiK3Tno (ORCPT ); Wed, 30 Nov 2022 14:43:44 -0500 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6ADB093A72 for ; Wed, 30 Nov 2022 11:43:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1669837423; x=1701373423; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=A7a9sqkLbE6Gtt15Ja5DbI50d22X6kyhB4O3QldroEU=; b=kzOhLKtOoamqE/UlJgpNh+spulgJmzAhzjDHTg/c6ZaYtlmfOnpVZvxm nOw/zcyYTIo9T9z05JI2XzPb8qiHdKeCF8M2e0Km/H0sdw2QgjfKimZGr 4/attlbl/zHR7tTQfQF00ksejjJTdKQYYdkn7iJZQrvJmSoxcdaS4dGER yEv1JwYSFGYVspa8lUDCTH/HHey37Yd30WTCOhLYEeHrvuCihIqcqYHxC /BtxsO/D8a0VtLAphAhsgSNJzq4mfsfn/Pj/38jf9x3Bu1UTZB6eOjwnO jXCbwv8ybNcd/ENz+fnGxjZ6o2sb2lnGUPsKWaSweGAn1sXNTxYx+q7DE A==; X-IronPort-AV: E=McAfee;i="6500,9779,10547"; a="303098376" X-IronPort-AV: E=Sophos;i="5.96,207,1665471600"; d="scan'208";a="303098376" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Nov 2022 11:43:41 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10547"; a="818752283" X-IronPort-AV: E=Sophos;i="5.96,207,1665471600"; d="scan'208";a="818752283" Received: from anguy11-desk2.jf.intel.com ([10.166.244.147]) by orsmga005.jf.intel.com with ESMTP; 30 Nov 2022 11:43:41 -0800 From: Tony Nguyen To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com, edumazet@google.com Cc: Jacob Keller , netdev@vger.kernel.org, anthony.l.nguyen@intel.com, richardcochran@gmail.com, Gurucharan G Subject: [PATCH net-next 04/14] ice: fix misuse of "link err" with "link status" Date: Wed, 30 Nov 2022 11:43:20 -0800 Message-Id: <20221130194330.3257836-5-anthony.l.nguyen@intel.com> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20221130194330.3257836-1-anthony.l.nguyen@intel.com> References: <20221130194330.3257836-1-anthony.l.nguyen@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org From: Jacob Keller The ice_ptp_link_change function has a comment which mentions "link err" when referring to the current link status. We are storing the status of whether link is up or down, which is not an error. It is appears that this use of err accidentally got included due to an overzealous search and replace when removing the ice_status enum and local status variable. Fix the wording to use the correct term. Signed-off-by: Jacob Keller Tested-by: Gurucharan G (A Contingent worker at Intel) Signed-off-by: Tony Nguyen --- drivers/net/ethernet/intel/ice/ice_ptp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/intel/ice/ice_ptp.c b/drivers/net/ethernet/intel/ice/ice_ptp.c index f93fa0273252..5607ec578499 100644 --- a/drivers/net/ethernet/intel/ice/ice_ptp.c +++ b/drivers/net/ethernet/intel/ice/ice_ptp.c @@ -1347,7 +1347,7 @@ int ice_ptp_link_change(struct ice_pf *pf, u8 port, bool linkup) if (ptp_port->port_num != port) return -EINVAL; - /* Update cached link err for this port immediately */ + /* Update cached link status for this port immediately */ ptp_port->link_up = linkup; if (!test_bit(ICE_FLAG_PTP, pf->flags)) -- 2.35.1