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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id EE591C4332F for ; Fri, 14 Jan 2022 22:10:17 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8406C6B018B; Fri, 14 Jan 2022 17:10:17 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 7C7146B018D; Fri, 14 Jan 2022 17:10:17 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 68D756B018E; Fri, 14 Jan 2022 17:10:17 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay033.a.hostedemail.com [64.99.140.33]) by kanga.kvack.org (Postfix) with ESMTP id 583C86B018B for ; Fri, 14 Jan 2022 17:10:17 -0500 (EST) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 21CD621ED3 for ; Fri, 14 Jan 2022 22:10:17 +0000 (UTC) X-FDA: 79030286874.02.F92B620 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by imf13.hostedemail.com (Postfix) with ESMTP id 9060E2000E for ; Fri, 14 Jan 2022 22:10:16 +0000 (UTC) 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 ams.source.kernel.org (Postfix) with ESMTPS id 7CFD9B8262F; Fri, 14 Jan 2022 22:10:15 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id F1162C36AE9; Fri, 14 Jan 2022 22:10:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1642198215; bh=0wpDmZGhi9LlL0lT+cuhNOqCuaItfO0G1UgkHf7/l5U=; h=Date:From:To:Subject:In-Reply-To:From; b=Bl8MD/34u6Vs4uMu7KpuR8P03BGSPRVxWmlLgQwH2fBGNlbW6A3Zf+10iU3yGKJ2N hpo3IAcNeRISuBTCc5/jZklv4jTlt8+QpWgZ6wJwnrvNDL1T7ubFfLDlpWgsBglZ28 4Vhgy5ATdLpJp2hpglxBVMNm/pB/lyhHIPl/KfGg= Date: Fri, 14 Jan 2022 14:10:14 -0800 From: Andrew Morton To: akpm@linux-foundation.org, corbet@lwn.net, linux-mm@kvack.org, mm-commits@vger.kernel.org, sj@kernel.org, torvalds@linux-foundation.org Subject: [patch 134/146] mm/damon: remove a mistakenly added comment for a future feature Message-ID: <20220114221014.MeoVZWm-2%akpm@linux-foundation.org> In-Reply-To: <20220114140222.6b14f0061194d3200000c52d@linux-foundation.org> User-Agent: s-nail v14.8.16 X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 9060E2000E X-Stat-Signature: zesrt6ib4bckw65sj88si63z5ckjwqi5 Authentication-Results: imf13.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b="Bl8MD/34"; spf=pass (imf13.hostedemail.com: domain of akpm@linux-foundation.org designates 145.40.68.75 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none X-HE-Tag: 1642198216-72663 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: From: SeongJae Park Subject: mm/damon: remove a mistakenly added comment for a future feature Due to a mistake in patches reordering, a comment for a future feature called 'arbitrary monitoring target support'[1], which is still under development, has added. Because it only introduces confusion and we don't have a plan to post the patches soon, this commit removes the mistakenly added part. [1] https://lore.kernel.org/linux-mm/20201215115448.25633-3-sjpark@amazon.com/ Link: https://lkml.kernel.org/r/20211209131806.19317-7-sj@kernel.org Fixes: 1f366e421c8f ("mm/damon/core: implement DAMON-based Operation Schemes (DAMOS)") Signed-off-by: SeongJae Park Cc: Jonathan Corbet Signed-off-by: Andrew Morton --- include/linux/damon.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/include/linux/damon.h~mm-damon-remove-a-mistakenly-added-comment-for-a-future-feature +++ a/include/linux/damon.h @@ -281,7 +281,7 @@ struct damon_ctx; * as an integer in [0, &DAMOS_MAX_SCORE]. * @apply_scheme is called from @kdamond when a region for user provided * DAMON-based operation scheme is found. It should apply the scheme's action - * to the region. This is not used for &DAMON_ARBITRARY_TARGET case. + * to the region. * @target_valid should check whether the target is still valid for the * monitoring. * @cleanup is called from @kdamond just before its termination. _