Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp334168pxf; Wed, 7 Apr 2021 00:10:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxKbDDaZtT+R6lxbM2k754Bo7/LPpJaH0GIOasqPXdM2VFgEkqR7sbVmZdYrWs1zkiS1NLd X-Received: by 2002:a05:6638:53b:: with SMTP id j27mr2113628jar.72.1617779428449; Wed, 07 Apr 2021 00:10:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617779428; cv=none; d=google.com; s=arc-20160816; b=R21ZWjKs7blmeq0ylyF0pmK0Llf308i/8i/70p1DojVYBydQswSrX8RAcF74kHxwlF UScjFzAdDiqc5N/B+P1sf4uvkeN3B2tHwW2GV6TYa4C1aHud1xZpQ75bBIWCSfdXoUho 62Z7xnHe10UvjrAZEzH4Dph7Rf/VQV2XlPPu43I64h31iHVMyjXfLJUGCqKCcVhMFmr5 W0a+UZc1t/LggnHkZMm+XKlS9uVRFWZ7PnWdzR9PcB3E7YWWCVqEP5qCL47ISKGKj+dJ 1xQ9gO6EZwf/PLej3GnFTBWh8PMZvVtJQfLThTpBvCXSuo0xM2eOq4ctH4s1q4wUasCe KGxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=8VocbV3u+tlrKZxZWpWibtk9bR6gRKsdOjfPLNUoKCg=; b=DMgXVxY0HGvmfEx2jOQyJKQoIOw7/fpibStpfVjjzK4J+S3DqTQpv0jXEuPafETNBj tPM9DPqsLmrJenn8++h+uqvJrRuXKgCsurA06jt0z6sc+P3ylNidHqD2D1MxQVXSGKQ+ 0yGDKBXpi/cvzEPPJkET4goo8U+3D/gsDxtu9UE4QV1T3sSr5UkdTFimbka+QVGBIU0v Cp2cbHbjESubx3gjoRrtOeLwrj0GpFxHMDbVsZuNFuSXdgY1O1Q6VMi9FwNpLaEO8qC4 hLSkNBoa4WaL4JacrUkyDOzVMNgnSubMyJuN+IMaI1o/l09NWgbMrfiVTpxWycVaJ7e6 6gtA== 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 q12si20011382ior.61.2021.04.07.00.10.14; Wed, 07 Apr 2021 00:10:28 -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 S1346180AbhDFQFm (ORCPT + 99 others); Tue, 6 Apr 2021 12:05:42 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:36142 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233361AbhDFQFj (ORCPT ); Tue, 6 Apr 2021 12:05:39 -0400 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1lToCh-00F94W-A1; Tue, 06 Apr 2021 18:05:23 +0200 Date: Tue, 6 Apr 2021 18:05:23 +0200 From: Andrew Lunn To: DENG Qingfang Cc: Chun-Kuang Hu , "David S. Miller" , Florian Fainelli , Heiner Kallweit , Jakub Kicinski , Landen Chao , Matthias Brugger , Russell King , Sean Wang , Vivien Didelot , Vladimir Oltean , Rob Herring , Linus Walleij , Greg Kroah-Hartman , Sergio Paracuellos , linux-kernel , "moderated list:ARM/Mediatek SoC support" , linux-staging@lists.linux.dev, DTML , netdev , Weijie Gao , Chuanhong Guo , =?iso-8859-1?Q?Ren=E9?= van Dorst Subject: Re: [RFC net-next 1/4] net: phy: add MediaTek PHY driver Message-ID: References: <20210406141819.1025864-1-dqfext@gmail.com> <20210406141819.1025864-2-dqfext@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 06, 2021 at 11:57:14PM +0800, DENG Qingfang wrote: > On Tue, Apr 6, 2021 at 11:47 PM Chun-Kuang Hu wrote: > > > > Hi, Qingfang: > > > > DENG Qingfang 於 2021年4月6日 週二 下午10:19寫道: > > > --- a/drivers/net/phy/Kconfig > > > +++ b/drivers/net/phy/Kconfig > > > @@ -207,6 +207,11 @@ config MARVELL_88X2222_PHY > > > Support for the Marvell 88X2222 Dual-port Multi-speed Ethernet > > > Transceiver. > > > > > > +config MEDIATEK_PHY > > > > There are many Mediatek phy drivers in [1], so use a specific name. > > So "MEDIATEK_MT7530_PHY" should be okay? No. MEDIATEK_PHY is consistent with other PHY drivers. Please leave it as it is. And with time, we expect other devices will be supported by this driver, so having MT7530 in the name would be confusing. Andrew