Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp2155456ybh; Fri, 17 Jul 2020 10:34:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzzIMZknlln9RwWPPTTtWhl8TYt5pxTJOwGpXS5ppenYdmov1C7TIhs5KoB9WhuoQM14U0Q X-Received: by 2002:a17:906:f98e:: with SMTP id li14mr9399119ejb.174.1595007241780; Fri, 17 Jul 2020 10:34:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595007241; cv=none; d=google.com; s=arc-20160816; b=SKhilznvsCVPKBix1KZ7TE3demYMvz0RtX3hzcPf+/4bqm9J9uEdK2dvLuB3JI0oUa VUInk5u9gbpcO/AcKvkBRoLphkI59amp6qWVxpqRb+vI1d4r3VhGSX+vb4tH+RgKzxPq QLnRiEy/s5YO0iEw0zmFjzW/cBE1fhlAHqg71iQ+clthtS8SPOebd0Id0DrqIvrjJ8Mv 8Za19ODVNcdS7/EGRjHgxCaWJq/JR6ZiwiDytCNUYIrLy8lvl8MMGcLd5N4uwyBXD4KM O16Up35txa4fYvaNTYaC09SS7uhj02ZsY7+yWScn5WXoQtqMkcGf0ktKxCUK/5DIJ2tU GxvQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=UxsVpqvUY/kvI50W3iSby2LUo+QjdXPSVp9CbrycXH0=; b=n4+hwjlVcnW3aSv3XgOpKLHxf4Y4jRBHslXIBR5vx4SZTVsMPsviYnKUVJhs5/C4hK effA7PyrV+6h7bKEW2gc96Kn3HLps2DZ3rLewcqdm6qyDRTyWPA66w/S9Q9CXV2Q3PQZ nldDg3rN8qD+NqBB9rJngGk4H3D4rjme3uEtC0VwzFDCcLKzgUvojHPEdmrsX4qHUTsQ vIeXDspo5MxEYe8Egrw4f9YmiN9FmTzM6G4xhQDcE7qP38YrSjKB1/eVmmjCpSe75dEE TM2T0WCKFLH8iLqDlkV7ZjxTm96BGMJnrBCKu4gVVLQg+i5m+ZGffbR6SqG7+XczKXXG 2QPw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id yj19si5574339ejb.410.2020.07.17.10.33.38; Fri, 17 Jul 2020 10:34:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726634AbgGQRdV (ORCPT + 99 others); Fri, 17 Jul 2020 13:33:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44330 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726090AbgGQRdV (ORCPT ); Fri, 17 Jul 2020 13:33:21 -0400 Received: from shards.monkeyblade.net (shards.monkeyblade.net [IPv6:2620:137:e000::1:9]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D70E9C0619D2; Fri, 17 Jul 2020 10:33:20 -0700 (PDT) Received: from localhost (unknown [IPv6:2601:601:9f00:477::3d5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id C7F58135E9FF1; Fri, 17 Jul 2020 10:33:19 -0700 (PDT) Date: Fri, 17 Jul 2020 10:33:18 -0700 (PDT) Message-Id: <20200717.103318.681710805820706586.davem@davemloft.net> To: cphealy@gmail.com Cc: linux@armlinux.org.uk, andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com, kuba@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next] net: phy: sfp: Cotsworks SFF module EEPROM fixup From: David Miller In-Reply-To: <20200714175910.1358-1-cphealy@gmail.com> References: <20200714175910.1358-1-cphealy@gmail.com> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Fri, 17 Jul 2020 10:33:20 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Chris Healy Date: Tue, 14 Jul 2020 10:59:10 -0700 > Some Cotsworks SFF have invalid data in the first few bytes of the > module EEPROM. This results in these modules not being detected as > valid modules. > > Address this by poking the correct EEPROM values into the module > EEPROM when the model/PN match and the existing module EEPROM contents > are not correct. > > Signed-off-by: Chris Healy Applied, thank you.