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.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 519B5C4338F for ; Tue, 27 Jul 2021 15:28:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2408061B3F for ; Tue, 27 Jul 2021 15:28:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237108AbhG0PZu (ORCPT ); Tue, 27 Jul 2021 11:25:50 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:47706 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236901AbhG0PZp (ORCPT ); Tue, 27 Jul 2021 11:25:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=dZk70SnxCgqV5ow1i0wJVGa22cxSQ4M4a5N6jVhB334=; b=yvMOVx7bbnhcjaK+bebVFBVHjb Zudg6uqBs082zvHsCFcf9sQkP/qAOUSut9Pn24mw+1A8kW/nCBun6z8yo0iiR+/pvpXc1DABfMnpl YyHlL9u45XvoCEu09u5qq0Eyk4k/SlaJFUo4GdAgey6zcklOQhF42M4mQKuUDcF+v7S4=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1m8Owo-00F27k-CN; Tue, 27 Jul 2021 17:24:46 +0200 Date: Tue, 27 Jul 2021 17:24:46 +0200 From: Andrew Lunn To: Michael Walle Cc: Marek =?iso-8859-1?Q?Beh=FAn?= , anthony.l.nguyen@intel.com, bigeasy@linutronix.de, davem@davemloft.net, dvorax.fuxbrumer@linux.intel.com, f.fainelli@gmail.com, hkallweit1@gmail.com, jacek.anaszewski@gmail.com, kuba@kernel.org, kurt@linutronix.de, linux-leds@vger.kernel.org, netdev@vger.kernel.org, pavel@ucw.cz, sasha.neftin@intel.com, vinicius.gomes@intel.com, vitaly.lifshits@intel.com Subject: Re: [PATCH net-next 5/5] igc: Export LEDs Message-ID: References: <20210727081528.9816-1-michael@walle.cc> <20210727165605.5c8ddb68@thinkpad> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-leds@vger.kernel.org > I wasn't talking about ethN being same as the network interface name. > For clarity I'll use ethernetN now. My question was why would you > use ethmacN or ethphyN instead if just ethernetN for both. What is > the reason for having two different names? We can get into the situation where both the MAC and the PHY have LED controllers. So we need to ensure the infrastructure we put in place handles this, we don't get any name clashes. Andrew