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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 2D44EC77B7F for ; Tue, 16 May 2023 15:15:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=pyvCmi2YlynIjKv3mukH2Ufsa/5daMUCnu0FG0M7RzE=; b=gsbGVaZ6dYV0ro WWDzByAaxvWAswBwUKdndCPswIv0lgwFrPYT+gwY1T3GO4cK0YEmsoTHHFA4cm5hRXU2cgC+YhSQI lro0c138Di085wKsdO5w3EptYyXMREv/BEbXZq8wI1D0rj2sEZ7JvqmJOpH2OGS28LXFMdIjOrnhm Rq5KUSV2GUEXQVEGUtO4FoI8wgY9LVd9u92lkAUCBIZ9RANCjb9Cl7Y6qCT/9GdM1gaRdRpRpIIjz ou4/ElS/VZrjshoD0B4R1t6mqrswGttCBJgJI2wj05+wMqaIzE8LcD/csBafc2MC/Fzh7Cg+z6Cs3 N67GL+3LxeGjU3nEzlUw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1pywO7-006D7s-0Q; Tue, 16 May 2023 15:14:55 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1pywO2-006D6c-0u for linux-arm-kernel@lists.infradead.org; Tue, 16 May 2023 15:14:53 +0000 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 CF3CF62A54; Tue, 16 May 2023 15:14:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CD57EC433EF; Tue, 16 May 2023 15:14:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1684250089; bh=QniIXIy0/udi6RAZEpqo+280u5VsJlOWjT6ntAhcq0k=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=QKDFi5+0/A7w2D68j7dEp4ovMsfX4TwmxYUB7fdWCOdP1VqFUdaF1zh1xQHBjnblw /OLtkB/iVjZEAZaEvSUlSnwVnnaAGNW9PTOwxxTx13CeMANJAO+dh2eYCpsSXe5Rt6 j/d7xOC+TJNjypEXsytSpogLjwr7Y3I6SY3lFKP9giuRQW/kF2ub1aZXocgZz+mxGo x5HzuqW81SXN02Rtd/ca3U8oK/xFvwqVXumzOFDB9iob1g/3RoMa7jjrVfmeEWkQgP M90oWaqZMY10yttCOX3sRfdMzHSUcPfdrKrrSqgspxFNF0Jhj28fF4uGo/koq7M+Ue 4bLmuXBf19I1A== From: Will Deacon To: Catalin Marinas Cc: kernel-team@android.com, Will Deacon , Andrew Morton , "Justin M . Forbes" , Mike Rapoport , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm64: Make the ARCH_FORCE_MAX_ORDER config input prompt unconditional Date: Tue, 16 May 2023 16:14:39 +0100 Message-Id: <168424974751.3556475.6986819045014675133.b4-ty@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20230503123342.90538-1-catalin.marinas@arm.com> References: <20230503123342.90538-1-catalin.marinas@arm.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230516_081452_042745_CCC6499B X-CRM114-Status: GOOD ( 12.21 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, 3 May 2023 13:33:42 +0100, Catalin Marinas wrote: > Commit 34affcd7577a ("arm64: drop ranges in definition of > ARCH_FORCE_MAX_ORDER") dropped the ranges from the config entry and > introduced an EXPERT condition on the input prompt instead. This change > may affect some distro kernels that change ARCH_FORCE_MAX_ORDER but do > not want to enable EXPERT. > > Drop EXPERT from the input prompt together with the (ARM64_4K_PAGES || > ARM64_16K_PAGES) condition as the latter no longer makes sense after the > ranges were removed. The latter makes all the page size configurations > consistent w.r.t. ARCH_FORCE_MAX_ORDER. > > [...] Applied to arm64 (for-next/fixes), thanks! [1/1] arm64: Make the ARCH_FORCE_MAX_ORDER config input prompt unconditional https://git.kernel.org/arm64/c/fd2d1cb8c545 Cheers, -- Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel