Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7BDFDC7618A for ; Wed, 15 Mar 2023 13:17:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231912AbjCONR1 (ORCPT ); Wed, 15 Mar 2023 09:17:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40656 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231937AbjCONRT (ORCPT ); Wed, 15 Mar 2023 09:17:19 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B4D9723C60; Wed, 15 Mar 2023 06:17:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1678886230; x=1710422230; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=1DQUI8x1dGKooP+0g0BDBbXwwTxIZZOldlQJxrEvwLU=; b=R/C90hMxoiZz6riV/4R/kK2kXhWjO3m0Ol+nvNkBmumsL1ViECVDmONJ vCvwhJyxnDjiaNimArqA2i3MQYTV04yFv5HdjA0A0YeJYxbk7Vs5OllwP 8DXNRKgZea/KmxlztwM4zsuePktpGzPup04nxkaRMmQACQK5rKbSYcpcH RKvEOq2YQOe4ZXrfbxuAXwD5btWuWGMQ+ItG8EGCYKviGW6JmdpSUa//p EP7pRDuior7axasmb3nzaSgwrMhj341BlH3v17+CvzutzKztkvKYSUON6 emt4zfCL2Oy5NPGjzQTqgrT5xM/RyEbAejW+Qyv/6hKEJLJdhKwq3xXag g==; X-IronPort-AV: E=McAfee;i="6500,9779,10649"; a="317350732" X-IronPort-AV: E=Sophos;i="5.98,262,1673942400"; d="scan'208";a="317350732" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Mar 2023 06:16:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10649"; a="743693190" X-IronPort-AV: E=Sophos;i="5.98,262,1673942400"; d="scan'208";a="743693190" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga008.fm.intel.com with ESMTP; 15 Mar 2023 06:16:46 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1pcQzj-003q8i-1V; Wed, 15 Mar 2023 15:16:43 +0200 Date: Wed, 15 Mar 2023 15:16:42 +0200 From: Andy Shevchenko To: Michal Swiatkowski Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Kurt Kanzenbach , Andrew Lunn , Florian Fainelli , Vladimir Oltean , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni Subject: Re: [PATCH net-next v6 1/1] net: dsa: hellcreek: Get rid of custom led_init_default_state_get() Message-ID: References: <20230314181824.56881-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 15, 2023 at 06:57:37AM +0100, Michal Swiatkowski wrote: > On Tue, Mar 14, 2023 at 08:18:24PM +0200, Andy Shevchenko wrote: > > LED core provides a helper to parse default state from firmware node. > > Use it instead of custom implementation. ... > You have to fix implict declaration of the led_init_default_state_get(). Seems like users have to choose between 'select NEW_LEDS' and 'depends on NEW_LEDS' in the Kconfig. > I wonder if the code duplication here can be avoided: Whether or not this is out of the scope of this patch. Feel free to submit one :-) ... > Only suggestion, patch looks good. Thank you! -- With Best Regards, Andy Shevchenko