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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 01CF3C433EF for ; Tue, 29 Mar 2022 12:25:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236350AbiC2M1j (ORCPT ); Tue, 29 Mar 2022 08:27:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55688 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232550AbiC2M1e (ORCPT ); Tue, 29 Mar 2022 08:27:34 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C43F44D9C1; Tue, 29 Mar 2022 05:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1648556751; x=1680092751; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=B4gfQZ727rl7OXibsvWflHV4WHOqBqSX/MZ7Umzjj+U=; b=hTOMwYLmd5r+rqE7BtdFiUKsn2Enep2Mdr/hIep4uQGm0f0IcAi58d0t PULxF3zK06I27mRsmOd5t4qwZCx16bDluOdf2XF7HkOyHAVgC7eVNiZNm ozb2NpuXNKgq4/XhqKdvETHMoM39ZB2YI8Mbh4CDPTSGPiSInjyxecZNW eVIs9931oGuS90Y2RvF3ptaA01BkU6G34Cy9DKFLrSrZXKnkyfLushqQm 3Ms/z3Y4iy5NRlS0oSSG1e1+Iy393TVHUhFeZJa8W4D8udllThbZGqf0Z LaDQ5gsW3uN/bb4h+BgJgp3kyxUoGfKQ4KYiJE/Q7Tj5D1CwfUdy0qGZA Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10300"; a="258065891" X-IronPort-AV: E=Sophos;i="5.90,220,1643702400"; d="scan'208";a="258065891" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Mar 2022 05:25:51 -0700 X-IronPort-AV: E=Sophos;i="5.90,220,1643702400"; d="scan'208";a="518900483" Received: from smile.fi.intel.com ([10.237.72.59]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Mar 2022 05:25:46 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nZAuN-008jlQ-PL; Tue, 29 Mar 2022 15:25:11 +0300 Date: Tue, 29 Mar 2022 15:25:11 +0300 From: Andy Shevchenko To: Fabien DESSENNE Cc: Gregory CLEMENT , Geert Uytterhoeven , Linus Walleij , linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, Neil Armstrong , Kevin Hilman , Jerome Brunet , Martin Blumenstingl , Andrew Lunn , Sebastian Hesselbarth , Maxime Coquelin , Alexandre Torgue , Bartosz Golaszewski Subject: Re: [PATCH v1 2/5] pinctrl: stm32: Replace custom code by gpiochip_count() call Message-ID: References: <20220325200338.54270-1-andriy.shevchenko@linux.intel.com> <20220325200338.54270-2-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 Tue, Mar 29, 2022 at 02:07:01PM +0200, Fabien DESSENNE wrote: > Hi Andy > > Thank you for your the clarification. > Reviewed-by: Fabien Dessenne Thanks! In v2 I'm going to add another patch and the first (against gpiolib) will be split to two. This patch will be almost unchanged: I've decided to rename gpiochip_count() to gpiochip_node_count(), otherwise it's the same. So, I'll keep your tag. -- With Best Regards, Andy Shevchenko