Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp412446pxb; Thu, 7 Apr 2022 08:47:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyOsphKNA8p0dSZfbPDCX+eog4ZqZlwkOfmztyFe9MlJs2A4OY0/IMryxXqa7awr4ILw0Yd X-Received: by 2002:a17:907:7f0f:b0:6e4:c15e:7751 with SMTP id qf15-20020a1709077f0f00b006e4c15e7751mr14167658ejc.266.1649346424183; Thu, 07 Apr 2022 08:47:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649346424; cv=none; d=google.com; s=arc-20160816; b=wjr7386jIQVV52cknpv1Jk/EOez3OQQGzHBw1o+udFZfU3Bz0UNltH7ykJ0n8C2KO9 eychtFM26p8SBjcRx6tOZAMKK3qSwQUHm/bC15mYIhSTwWX2bwVuW0+yF6K5JW59RQBS soJz5CLNl2qVyCoV1cb8sVPFfuoMcIkcZ4F8kkDXOgx3j/Z/u6x+RhafQEkVhYE1Tk1y swpNVPWZvKFf6lHSHholUcP2DMbm6Enu6PMKAWAJWrGBMeSLXrhc0+OVW/rzx/uoJnt3 3XvYqoD6YKKRd0f3eDsafD28+BnC4FLf17B8msNJSqbFxmSRTs8fC+GGDqzDBt1C0bE/ ECfg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=OrAVdtI06jlWzu77PZjIBfUVfDfo5qupQAsNYfVHmic=; b=oyyTmrI1AGzZqXmAoWHFRTGLqSV/QmYFUcFH0s2Iv4oiokKmxBCDxBsM8IsumRCXrZ Jm1WdbcSewUo94nIMSWehLSUhuI3CiiJFIrqmRtCUQQFPRLpJnDdWa+tWeZu+8wskjvZ YjZXylg2Xon3eGDhNseZ+dJymD0mQ1JDRr8wEd8IXUt+/43AJCOxNq5fcMVBAavRumQ1 c0/NS19P5xgxExDFQYjKf71qe/xsYQoO4nL07yR+pih2NHK74lHSdu9ww7033ijkRLBo +f7MlHb1jMemnYJJgzylqbsde/Pa+T/y3N5TmWReOHRPabJhqtnz0+OKonqcI/OVONSF Bcpw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=REyfza79; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id gy3-20020a170906f24300b006e0d34b7daesi14774388ejb.908.2022.04.07.08.46.30; Thu, 07 Apr 2022 08:47:04 -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=@messagingengine.com header.s=fm3 header.b=REyfza79; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243163AbiDGIg3 (ORCPT + 99 others); Thu, 7 Apr 2022 04:36:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52322 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242813AbiDGIgZ (ORCPT ); Thu, 7 Apr 2022 04:36:25 -0400 Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4C20124A74E; Thu, 7 Apr 2022 01:34:24 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id A93533201D51; Thu, 7 Apr 2022 04:34:20 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 07 Apr 2022 04:34:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; 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:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=OrAVdtI06jlWzu77P ZjIBfUVfDfo5qupQAsNYfVHmic=; b=REyfza793XvLwCmAbyDR3j41ku76wmjj9 t8ZPCQN8csyCmQMKvB42XV1AmWwt4wNNrxmwPC81RF5b8fAADR0pQalFI8qXYPT0 7/q14rkEhdtYWx6Ir/coc19eP4KQ2iDLO5MNs9cjC74Tfci0AMnCeGRILehn1Tbg zdS1YIVs1JnZtUmSbl0qDXyVGx7RDN2AtppERAi3Ke56NSptXrFZhqEyJaH0jf/o R7Q19bQDBPRh9KMpteNmIHQXlpkVdxrVY6aYJfkMqCrUCBayiLSBrdr/ZXf3zR2b tu/TkEybMrURbop9YitH5hmy4TK32Gu+HMKnytWHiS9lprsHPdZhg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudejkedgtdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffujgfkfhggtgesthdtredttddtvdenucfhrhhomhephfhinhhnucfv hhgrihhnuceofhhthhgrihhnsehlihhnuhigqdhmieekkhdrohhrgheqnecuggftrfgrth htvghrnhepffduhfegfedvieetudfgleeugeehkeekfeevfffhieevteelvdfhtdevffet uedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepfh hthhgrihhnsehlihhnuhigqdhmieekkhdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 7 Apr 2022 04:34:17 -0400 (EDT) Date: Thu, 7 Apr 2022 18:34:15 +1000 (AEST) From: Finn Thain To: John Paul Adrian Glaubitz cc: Arnd Bergmann , Rob Landley , Geert Uytterhoeven , Christoph Hellwig , Linus Torvalds , Yoshinori Sato , Linux Kernel Mailing List , linux-arch , "moderated list:H8/300 ARCHITECTURE" , "open list:TENSILICA XTENSA PORT (xtensa)" , Max Filippov , Linux-sh list , linux-m68k , Greg Ungerer , Damien Le Moal , linux-riscv , Rich Felker Subject: Re: [RFC PULL] remove arch/h8300 In-Reply-To: <04c0374f-0044-c84d-1820-d743a4061906@physik.fu-berlin.de> Message-ID: References: <04c0374f-0044-c84d-1820-d743a4061906@physik.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL, SPF_HELO_PASS,SPF_NONE,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 Thu, 7 Apr 2022, John Paul Adrian Glaubitz wrote: > On 4/7/22 09:17, Arnd Bergmann wrote: > > On Wed, Apr 6, 2022 at 11:25 PM Rob Landley wrote: > > > >> I'm interested in H8300 because it's a tiny architecture (under 6k > >> lines total, in 93 files) and thus a good way to see what a minimal > >> Linux port looks like. If somebody would like to suggest a different > >> one for that... > > > > Anything that is maintained is usually a better example, and it helps > > when the code is not old enough to have accumulated a lot of historic > > baggage. > > But if it's not a lot of code, would it really accumulate a lot of > cruft? > Where you see "TODO" in Documentation/features/*/*/arch-support.txt it may mean that an architecture is preventing the removal of an old API. You're quite right, though, it is incorrect to call this an "accumulation" of baggage. It is actually the failure to remove cruft. (OTOH, shiny new things can be said to "accumulate". That's how cruft gets made.)