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=-4.2 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_PASS 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 B2E9DC43381 for ; Tue, 19 Feb 2019 05:35:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8177A217D7 for ; Tue, 19 Feb 2019 05:35:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="mDkMz3CX" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725826AbfBSFfX (ORCPT ); Tue, 19 Feb 2019 00:35:23 -0500 Received: from fllv0016.ext.ti.com ([198.47.19.142]:55322 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725768AbfBSFfX (ORCPT ); Tue, 19 Feb 2019 00:35:23 -0500 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id x1J5ZDWe042350; Mon, 18 Feb 2019 23:35:13 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1550554513; bh=RlpsfohgMuptkbeqKeR6AhZ0hIwKhcV0nqmBT35oVLg=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=mDkMz3CXuamoipz61nr7w/e5VvhgaIu/zG/00gZPnpAsz1rjRE2BMA+qOO+yhl9kI IjkUMo14jMvl3FLECM/EyJc2e1168yhVi7nbSi1JM/Rg2nWAwmo09TEG49p0uca9Ym PRFggzevpNM9deomwoGfznJVs2PDM7so1KlJp4Og= Received: from DLEE107.ent.ti.com (dlee107.ent.ti.com [157.170.170.37]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x1J5ZDPI070449 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 18 Feb 2019 23:35:13 -0600 Received: from DLEE109.ent.ti.com (157.170.170.41) by DLEE107.ent.ti.com (157.170.170.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 18 Feb 2019 23:35:13 -0600 Received: from dlep32.itg.ti.com (157.170.170.100) by DLEE109.ent.ti.com (157.170.170.41) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1591.10 via Frontend Transport; Mon, 18 Feb 2019 23:35:13 -0600 Received: from [172.24.190.172] (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep32.itg.ti.com (8.14.3/8.13.8) with ESMTP id x1J5Z9p0006715; Mon, 18 Feb 2019 23:35:10 -0600 Subject: Re: [PATCH v2 1/2] net: phy: at803x: dont inline helpers To: Vinod Koul , David Miller CC: , , , , , , , References: <20190218101853.4290-1-vkoul@kernel.org> <20190218.162850.1254388175691397706.davem@davemloft.net> <20190219050227.GT21884@vkoul-mobl> From: Sekhar Nori Message-ID: <26c3046d-8b1c-e601-7cad-c9a7bc267033@ti.com> Date: Tue, 19 Feb 2019 11:05:09 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190219050227.GT21884@vkoul-mobl> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi Vinod, On 19/02/19 10:32 AM, Vinod Koul wrote: > Hello Dave, > > On 18-02-19, 16:28, David Miller wrote: >> From: Vinod Koul >> Date: Mon, 18 Feb 2019 15:48:52 +0530 >> >>> Some helpers were inlined, but makes more sense to allow compiler >>> to do the right optiomazations instead, so remove inline for >>> at803x_disable_rx_delay() and at803x_disable_tx_delay() >>> >>> Signed-off-by: Vinod Koul >> >> Two problem with this patch series. >> >> 1) It fixes a bug in 'net' but the patches only apply cleanly to >> 'net-next'. Please respin this against 'net'. > > I assume the 'net' is fixes going into current -rcX. This fixes issues > reported on linux-next due to patches in net-next, so these fixes should > go to net-next as well. net-next should be part of subject prefix in this case. See Documentation/networking/netdev-FAQ.rst Thanks, Sekhar