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=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_PASS,URIBL_BLOCKED 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 DCA19C169C4 for ; Fri, 8 Feb 2019 09:23:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A40B621919 for ; Fri, 8 Feb 2019 09:23:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="fYpwcxzA" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726601AbfBHJX0 (ORCPT ); Fri, 8 Feb 2019 04:23:26 -0500 Received: from fllv0015.ext.ti.com ([198.47.19.141]:55434 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725998AbfBHJX0 (ORCPT ); Fri, 8 Feb 2019 04:23:26 -0500 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id x189N3VO082505; Fri, 8 Feb 2019 03:23:03 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1549617783; bh=X/lGZNH3s/0L7uZkitokagWbtF0cFHSOQuQygwXIy+A=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=fYpwcxzAAXZKbtIbasmTIVsTU20vKtEMdixvw3lCzuwaLVLBBvl/OqBoOx37VtIHG hAELPoY8qHrx3HbcfEWdpiAWBKFT0nFzBp0Ncu0qXvL/3IVoSsjlLyK6DQ0kY8+jrk FnoPzskjYGt67nkYUkyrcsLeuhWqVn2PYvFwxo2Y= Received: from DFLE112.ent.ti.com (dfle112.ent.ti.com [10.64.6.33]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x189N2gV099195 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 8 Feb 2019 03:23:03 -0600 Received: from DFLE114.ent.ti.com (10.64.6.35) by DFLE112.ent.ti.com (10.64.6.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Fri, 8 Feb 2019 03:23:02 -0600 Received: from dflp32.itg.ti.com (10.64.6.15) by DFLE114.ent.ti.com (10.64.6.35) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1591.10 via Frontend Transport; Fri, 8 Feb 2019 03:23:02 -0600 Received: from [172.24.190.233] (ileax41-snat.itg.ti.com [10.172.224.153]) by dflp32.itg.ti.com (8.14.3/8.13.8) with ESMTP id x189Mwil016204; Fri, 8 Feb 2019 03:22:58 -0600 Subject: Re: [PATCH net-next v2 0/6] Add comphy support for Armada 38x To: Thomas Petazzoni , David Miller CC: , , , , , , , , , References: <20190207161825.ueinmyf6ygjiqzzy@shell.armlinux.org.uk> <20190207.181049.1229639710283404215.davem@davemloft.net> <20190208085821.7556a18d@windsurf> From: Kishon Vijay Abraham I Message-ID: <295924f0-1007-4b39-189b-1b21e4bf1b86@ti.com> Date: Fri, 8 Feb 2019 14:52:26 +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: <20190208085821.7556a18d@windsurf> 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, On 08/02/19 1:28 PM, Thomas Petazzoni wrote: > Hello David, > > On Thu, 07 Feb 2019 18:10:49 -0800 (PST) > David Miller wrote: > >> From: Russell King - ARM Linux admin >> Date: Thu, 7 Feb 2019 16:18:25 +0000 >> >>> This series adds support for the comphy for Armada 38x, which allows >>> these SoCs to use 2500BASE-X mode with appropriate SFP modules. >>> >>> Tested on SolidRun Clearfog after updating for the 5.0 merge window >>> changes. >> >> Series applied, thanks Russell. > > This series contained: > > - Device Tree bindings that had not been ACKed by the DT bindings > maintainers, one of which should have been merged through the > drivers/phy maintainer tree. > > - A brand new drivers/phy driver that had not been ACKed by the > drivers/phy maintainer. The PHY driver looks good to me. But I think it might still be better to take it via PHY tree since there are other Marvell drivers that are getting merged and will result in conflicts in Kconfig and Makefile. Thanks Kishon