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 04A42C6FA8A for ; Wed, 14 Sep 2022 13:04:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229714AbiINNEX (ORCPT ); Wed, 14 Sep 2022 09:04:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36708 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229510AbiINNEW (ORCPT ); Wed, 14 Sep 2022 09:04:22 -0400 Received: from wnew1-smtp.messagingengine.com (wnew1-smtp.messagingengine.com [64.147.123.26]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9286C6C76B; Wed, 14 Sep 2022 06:04:17 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.west.internal (Postfix) with ESMTP id B55D82B05D9C; Wed, 14 Sep 2022 09:04:12 -0400 (EDT) Received: from imap51 ([10.202.2.101]) by compute3.internal (MEProxy); Wed, 14 Sep 2022 09:04:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arndb.de; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1663160652; x=1663164252; bh=8JfDZhGhDT nn1MAP2k2cOZYtoltqkx4/4nhZ1F4oVjI=; b=QDwr9SP7k1+Rj0nzhL5WKBQMDL sNTfbUpxIfB3tqtQq12h0/L2PRquqoSfuoYUaaycp/EqwHZvflbQwhxse6kOObuO NKc/y7tHADHGfaaRjuMmv0XTMceixzHeQXl7uySZ9cYZcynJeTtuC909Z5E3Trfd T8W3owPE4ElN3mV06XJKBBfLqbt8E2z2gp+LEBVQ+ZvSsZxwaSxhCv1KBGb+sXFw eUDOVZKV1YQfeKagI74PIBBhr3FAxn8trX9WSwNqLXXCClm/r9U20TNEPiDD2KyC GGtA+/nmj4Fsd8Njn8L+Zp5rpWEbGwUU1O0oMQqZPSPoMOUgG59xgv//LmRw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1663160652; x=1663164252; bh=8JfDZhGhDTnn1MAP2k2cOZYtoltq kx4/4nhZ1F4oVjI=; b=0wnZz1ZSbLPgR4yFtqMTBONUEFWQrj+tHyZmktK7ETNW KE7PHz3c/pjFHiFG29UngXbh34qegeLtgUwTlrNweGyouPfxs67G4SWH6x27s7Ff geGW5pIKTpVsGC1wacj884HLBb+FtSB9iRyZJp1Z1dSAUYnyH4ZmachyHWiy7NOL dov7QhBV7SSzBuE0/NLu+IOJ4JozlOp1HUsp7lit+Pwj/tYAivPUyzZ46atW6vSt rcjTWm7sIE0UE/2MaD8b7rwXXNfM1hDAWtBN2jlMfFHCNsMatr/rWSU8d2p79R1g k7gOTZQlSD1mTD7XvBKFKUWDFW+IXK5IpN/YzZENfg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeduiedgiedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtsehttdertderredtnecuhfhrohhmpedftehr nhguuceuvghrghhmrghnnhdfuceorghrnhgusegrrhhnuggsrdguvgeqnecuggftrfgrth htvghrnhepvefhffeltdegheeffffhtdegvdehjedtgfekueevgfduffettedtkeekueef hedunecuffhomhgrihhnpehkvghrnhgvlhdrohhrghenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrrhhnugesrghrnhgusgdruggv X-ME-Proxy: Feedback-ID: i56a14606:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 918E0B60086; Wed, 14 Sep 2022 09:04:10 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-934-g6274855a4c-fm-20220913.002-g6274855a Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Wed, 14 Sep 2022 15:03:50 +0200 From: "Arnd Bergmann" To: "Linus Walleij" , "Andy Shevchenko" Cc: "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) Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Wed, Sep 14, 2022, at 2:38 PM, 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? I think the explanation given by Davide and Alessandro was rather detailed already: https://lore.kernel.org/lkml/Yw3LQjhZWmZaU2N1@arcana.i.gnudd.com/ https://lore.kernel.org/lkml/Yw3DKCuDoPkCaqxE@arcana.i.gnudd.com/ Arnd