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=-5.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 F203AC433E0 for ; Thu, 4 Jun 2020 16:38:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C83592072E for ; Thu, 4 Jun 2020 16:38:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="QYcyKHpr" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729864AbgFDQi0 (ORCPT ); Thu, 4 Jun 2020 12:38:26 -0400 Received: from lelv0143.ext.ti.com ([198.47.23.248]:52488 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729582AbgFDQi0 (ORCPT ); Thu, 4 Jun 2020 12:38:26 -0400 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 054GcKHF027568; Thu, 4 Jun 2020 11:38:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1591288700; bh=vJwfnPNsDW10qGjBVrg/CcyYGe7pIosmHJH5uBXXtM8=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=QYcyKHprrCdougNHZgK9/S9X65VMDx3mo+KqQHXacswEaFCEjv/nFI3Q3nciMwkVo SxdzOP6FRRZ7oPIXwcqnwsY6Ddnh+yRYSX9VSXdnLD8GWCUIyl71Mdat3J+2aL1YSy GadSGYh8lW40j79lDcjJ6K2QUDLpMTAkrfvbw1ak= Received: from DLEE112.ent.ti.com (dlee112.ent.ti.com [157.170.170.23]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 054GcKs4071393 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 4 Jun 2020 11:38:20 -0500 Received: from DLEE103.ent.ti.com (157.170.170.33) by DLEE112.ent.ti.com (157.170.170.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3; Thu, 4 Jun 2020 11:38:20 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE103.ent.ti.com (157.170.170.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3 via Frontend Transport; Thu, 4 Jun 2020 11:38:20 -0500 Received: from [10.250.52.63] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 054GcJ1c055968; Thu, 4 Jun 2020 11:38:19 -0500 Subject: Re: [PATCH net-next v6 4/4] net: dp83869: Add RGMII internal delay configuration To: Jakub Kicinski CC: , , , , , , , References: <20200604111410.17918-1-dmurphy@ti.com> <20200604111410.17918-5-dmurphy@ti.com> <20200604092545.40c85fce@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> From: Dan Murphy Message-ID: <63a53dad-4f0a-31ca-ad1a-361b633c28bf@ti.com> Date: Thu, 4 Jun 2020 11:38:14 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200604092545.40c85fce@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jakub On 6/4/20 11:25 AM, Jakub Kicinski wrote: > On Thu, 4 Jun 2020 06:14:10 -0500 Dan Murphy wrote: >> Add RGMII internal delay configuration for Rx and Tx. >> >> Signed-off-by: Dan Murphy > Hi Dan, please make sure W=1 C=1 build is clean: > > drivers/net/phy/dp83869.c:103:18: warning: ‘dp83869_internal_delay’ defined but not used [-Wunused-const-variable=] > 103 | static const int dp83869_internal_delay[] = {250, 500, 750, 1000, 1250, 1500, > | ^~~~~~~~~~~~~~~~~~~~~~ I built with W=1 and C=1 and did not see this warning. What defconfig are you using? Can you check if CONFIG_OF_MDIO is set or not?  That would be the only way that warning would come up. > Also net-next is closed right now, you can post RFCs but normal patches > should be deferred until after net-next reopens. I know net-next is closed. I pinged David M when it was open about what is meant by "new" patches in the net-dev FAQ.  So I figured I would send the patches to see what the response was. To me these are not new they are in process patches.  My understand is New is v1 patchesets. But now I have the answer. Dan