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 021C2C4332F for ; Mon, 17 Oct 2022 12:11:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229920AbiJQML1 (ORCPT ); Mon, 17 Oct 2022 08:11:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48794 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229817AbiJQML0 (ORCPT ); Mon, 17 Oct 2022 08:11:26 -0400 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 00161616D; Mon, 17 Oct 2022 05:11:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1666008686; x=1697544686; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=vw+vsrxvR88sMwvNZcFQAh9PSKUEFTkb+Zwafmh+7Zc=; b=fWOZnyW+oiYTGSuZbbfMz3vA0vqVNmuyt4y769FIYAh6qzXNqEx7ykFf IOiAwtIIYAEbev+TI3Rhlsz6lx7/wDwqV6gjFfT53m/+VV23p5ygT8Tk+ 7LIlE5FD+f42MAZkXbiPtXh2C3wmxm0kuO/aggOloMoUd5qua4aS21/Jy rtKBM3uLRELeYcC5pzfwERkdGUahEgPqpcCycb2k1RL/Vm69oPVaMqE4S slspkDgAXrVVDSvSW9Ru0AjW/jkHA1tlPihIxTCUaQ6wOh2cxSJ2E4nhs 1E9FY6wUB+UNDV6acnwluNZy7LvOjjsA7Z+UT8CJlCwKWTLPqWNMSJJJb w==; X-IronPort-AV: E=McAfee;i="6500,9779,10502"; a="306860556" X-IronPort-AV: E=Sophos;i="5.95,191,1661842800"; d="scan'208";a="306860556" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Oct 2022 05:11:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10502"; a="691335698" X-IronPort-AV: E=Sophos;i="5.95,191,1661842800"; d="scan'208";a="691335698" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga008.fm.intel.com with ESMTP; 17 Oct 2022 05:11:20 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1okOxh-008mX9-1M; Mon, 17 Oct 2022 15:11:17 +0300 Date: Mon, 17 Oct 2022 15:11:17 +0300 From: Andy Shevchenko To: Linus Walleij Cc: Bartosz Golaszewski , Christophe Leroy , Arnd Bergmann , Geert Uytterhoeven , Keerthy , Russell King , Jonathan Corbet , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" , Catalin Marinas , Will Deacon , Davide Ciminaghi , Linux Kernel Mailing List , "open list:GPIO SUBSYSTEM" , Linux ARM , Linux-Arch , linux-doc , "x86@kernel.org" Subject: Re: [PATCH v2 0/9] gpio: Get rid of ARCH_NR_GPIOS (v2) Message-ID: References: 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-gpio@vger.kernel.org On Mon, Oct 17, 2022 at 11:06:49AM +0200, Linus Walleij wrote: > On Mon, Oct 17, 2022 at 11:05 AM Bartosz Golaszewski wrote: ... > Let's test it in linux-next we need wide coverage for this. Yes, I believe the best if we can have this in the Linux Next as long as possible before going to upstream. This is good change that needs good testing coverage. Speaking of the latter, and a bit of offtopic, I want to send a PR of cleaning up the headers in pin control subsystem as soon as possible with the same rationale underneath, i.e. testing and new drivers using a cleaned up headers.. -- With Best Regards, Andy Shevchenko