Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp7916224rwn; Wed, 14 Sep 2022 06:27:58 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6OdLuO9UcCJTq7SgPqxAOd7rImaNb5/I0IXnJvjfm26PQKIcOc7voKSvnon6FxpCc7QBe9 X-Received: by 2002:aa7:d785:0:b0:452:dfa2:bb17 with SMTP id s5-20020aa7d785000000b00452dfa2bb17mr1293008edq.407.1663162078150; Wed, 14 Sep 2022 06:27:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663162078; cv=none; d=google.com; s=arc-20160816; b=fwP1yB+cEhomIv+yRUYTJ63ZV5TuU/1G50drX0yvrfO4u1gGL7dBy2OXp0zSu3V/Mg aOlM/Hbqnu6U33cO8aSR3Bd61D4NQzulaRCRi9+AXaRiXJ3hQ4oDg8XiN6KP7D8W9x9m uOweqxJTL/D44NxM/TBVbg8lp1l5PAvlOgbx5mh8AInD5mcSr36XZKVVpZGkgDG4ITN0 3Hmb8dtUcO/F+e1Tc1Pj7TxfPyCU+g1RPOQ9v6lnLpPE5Pxe629kqbwutaEaA+N5SeaJ flo7dp91R/oVr6qIMfQgLWhiQ9laKnYDMUIeBjqVZWicKFWvp8kh9yuwwgrfLxPiAdIg Kaog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:organization:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=af8RfvMhgT4Lphb6XvF/2pfHG6TZ1e6xt9yGGUY40wU=; b=PEgITrh6f7YOTjnuJkrsJ+sxZZqqbOmfhxpJ8sGcloStTkr1+kGIt3zjFV0+SEDr1J oeHtCztkdm3WvC7DE8POK64oSBcpXuzwY9hMcEi+M9RKHLx1TIm2GppEfbzCFn/2mpZg TBe7GCcViTnJstd45JD4SaNIdpGyzguca8/kXH7wLAS+2QlfxQxlZWv0tFYjqAlpZ0KP BWDl50tMTqxPcr4MML/VY/tQQVPFgDH0ECVV4JNykn+PTUPkiQfFUmmgtHBggIA8Q+kP shY8bmm36eK7D4FQWkdNaRUQ6bYQjwhVk3uKQxiVR8tgvRWhiqhnRfyuk+3o/OKdYN1a KcSA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=NclA4GOA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id mp11-20020a1709071b0b00b00778857eda1bsi14847729ejc.514.2022.09.14.06.27.29; Wed, 14 Sep 2022 06:27:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=NclA4GOA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229480AbiINNDM (ORCPT + 99 others); Wed, 14 Sep 2022 09:03:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36032 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229714AbiINNDK (ORCPT ); Wed, 14 Sep 2022 09:03:10 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 01E2D6051C; Wed, 14 Sep 2022 06:03:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663160589; x=1694696589; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=G3nunHZw0HXOmsMTYrHCL5+tpvupI1xxfdIlN7QmvpA=; b=NclA4GOAqf5IuV9ARazQllWaZd6E/CtojvPWu/+mT0bAQ6ztpjJ+Hc5c P6e24wgjIFGACF2a9iggD1HA8WForMbBEtKclz2iUORfCQf+vg09+4zM8 Q1xncSSzQpO5J5HSf0OWtO5SgsuRg3cr0Z2Hr1YPPVhG3qPbY3wWMq0vl YmVatzY3kGNceHNTpiSgqdOzEHEN6h21Y/wN8IymC2cWlQQ4WNBGcaXiu G1B5QFFI6Kf5isUvreRZZBQH7dcpIqexA1y90/0LfC4NkTZpo7vMSw+Lf JXgQvD9tVZimTvBUE58kyghA1BNcdx4YwhEFhfQOk+oTPw+FCOxMz9dG9 A==; X-IronPort-AV: E=McAfee;i="6500,9779,10470"; a="278808403" X-IronPort-AV: E=Sophos;i="5.93,315,1654585200"; d="scan'208";a="278808403" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2022 06:03:08 -0700 X-IronPort-AV: E=Sophos;i="5.93,315,1654585200"; d="scan'208";a="616856582" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2022 06:03:02 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oYS2c-002DBl-1B; Wed, 14 Sep 2022 16:02:58 +0300 Date: Wed, 14 Sep 2022 16:02:58 +0300 From: Andy Shevchenko To: Linus Walleij Cc: Arnd Bergmann , Bartosz Golaszewski , Christophe Leroy , 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 X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 14, 2022 at 02:38:53PM +0200, Linus Walleij wrote: > On Wed, Sep 7, 2022 at 12:15 PM Arnd Bergmann wrote: > > > >> drivers/gpio/gpio-sta2x11.c | 411 ----------------------- > (...) > > sta2x11 is an x86 driver, so not my area, but I think it would be > > best to kill off the entire platform rather than just its gpio > > driver, since everything needs to work together and it's clearly > > not functional at the moment. > > > > $ git grep -l STA2X11 > > Documentation/admin-guide/media/pci-cardlist.rst > > arch/x86/Kconfig > > arch/x86/include/asm/sta2x11.h > > arch/x86/pci/Makefile > > arch/x86/pci/sta2x11-fixup.c > > drivers/ata/ahci.c > > drivers/gpio/Kconfig > > drivers/gpio/Makefile > > drivers/gpio/gpio-sta2x11.c > > drivers/i2c/busses/Kconfig > > drivers/media/pci/Makefile > > drivers/media/pci/sta2x11/Kconfig > > drivers/media/pci/sta2x11/Makefile > > drivers/media/pci/sta2x11/sta2x11_vip.c > > drivers/media/pci/sta2x11/sta2x11_vip.h > > drivers/mfd/Kconfig > > drivers/mfd/Makefile > > drivers/mfd/sta2x11-mfd.c > > include/linux/mfd/sta2x11-mfd.h > > > > Removing the other sta2x11 bits (mfd, media, x86) should > > probably be done through the respective tree, but it would > > be good not to forget those. > > Andy is pretty much default x86 platform device maintainer, maybe > he can ACK or brief us on what he knows about the status of > STA2x11? Actually I have no idea about STA2x11, but in some thread I have noticed that there were people who know more on the topic and they told that removal is the right thing to do. Not sure how it should be done practically (driver-by-driver or altogether), Acked-by: Andy Shevchenko for either of the variants if it helps. -- With Best Regards, Andy Shevchenko