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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D1AE8C76195 for ; Thu, 23 Mar 2023 09:23:12 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4Pj0Hy5kzJz3f4t for ; Thu, 23 Mar 2023 20:23:10 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=FvLGPcFN; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=139.178.84.217; helo=dfw.source.kernel.org; envelope-from=rppt@kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=FvLGPcFN; dkim-atps=neutral Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4Pj0Gx2LBhz3bdV for ; Thu, 23 Mar 2023 20:22:17 +1100 (AEDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 2EDFE62564; Thu, 23 Mar 2023 09:22:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 81329C433A0; Thu, 23 Mar 2023 09:22:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1679563333; bh=D35W3oT4dEB7lQGf2gyibA65I3USxy0/PoMsBYvdggw=; h=From:To:Cc:Subject:Date:From; b=FvLGPcFNvposDJHd12P4B6tiY0alzsOWKmMDuuC6Bbtu7FQoT8X1aprZqvi0FJfLS mt0kh+Jo3486s1qGacqEDX/OHvGQZOMLk3QivFrdR+KFUHaYTxUB878ydKgR4ebxQD hFtgvnKM+VqXPQFFh+LsJ24F5Nvj1PwRnlN6oaSMVilDaV5obtUxIDQf1ebqfjw/// Xh234xD1rgyjvmGU7SMuN7Gnez8IKfnGstw+tdb8tErfz4SpbTfAXlP81Ofg/1ejcw 5ntVdo/7OGVtej0l0Oes4NXXVkuGPAKtpkLi1VbVSLZcdokDBgJOW5/iwZAcLFvNjO EHVKriGuB7TNg== From: Mike Rapoport To: Andrew Morton Subject: [PATCH 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER Date: Thu, 23 Mar 2023 11:21:42 +0200 Message-Id: <20230323092156.2545741-1-rppt@kernel.org> X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Rich Felker , linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, Catalin Marinas , Max Filippov , Guo Ren , linux-csky@vger.kernel.org, sparclinux@vger.kernel.org, Will Deacon , Yoshinori Sato , Russell King , Geert Uytterhoeven , Zi Yan , linux-xtensa@linux-xtensa.org, Arnd Bergmann , linux-m68k@lists.linux-m68k.org, John Paul Adrian Glaubitz , linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Dinh Nguyen , "Kirill A. Shutemov" , linuxppc-dev@lists.ozlabs.org, "David S. Miller" , Mike Rapoport Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" From: "Mike Rapoport (IBM)" Hi, Several architectures have ARCH_FORCE_MAX_ORDER in their Kconfig and they all have wrong and misleading prompt and help text for this option. Besides, some define insane limits for possible values of ARCH_FORCE_MAX_ORDER, some carefully define ranges only for a subset of possible configurations, some make this option configurable by users for no good reason. This set updates the prompt and help text everywhere and does its best to update actual definitions of ranges where applicable. Mike Rapoport (IBM) (14): arm: reword ARCH_FORCE_MAX_ORDER prompt and help text arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text csky: drop ARCH_FORCE_MAX_ORDER ia64: don't allow users to override ARCH_FORCE_MAX_ORDER m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER sh: reword ARCH_FORCE_MAX_ORDER prompt and help text sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text xtensa: reword ARCH_FORCE_MAX_ORDER prompt and help text arch/arm/Kconfig | 16 +++++++++------- arch/arm64/Kconfig | 27 ++++++++++++--------------- arch/csky/Kconfig | 4 ---- arch/ia64/Kconfig | 3 +-- arch/m68k/Kconfig.cpu | 16 +++++++++------- arch/nios2/Kconfig | 17 +++++++++-------- arch/powerpc/Kconfig | 22 +++++++++------------- arch/sh/mm/Kconfig | 19 +++++++++---------- arch/sparc/Kconfig | 16 +++++++++------- arch/xtensa/Kconfig | 16 +++++++++------- 10 files changed, 76 insertions(+), 80 deletions(-) base-commit: 51551d71edbc998fd8c8afa7312db3d270f5998e -- 2.35.1