From nobody Fri Nov 29 05:40:37 2024 Received: from xavier.telenet-ops.be (xavier.telenet-ops.be [195.130.132.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C2EA6824AD for ; Tue, 24 Sep 2024 11:55:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=195.130.132.52 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727178924; cv=none; b=tN7uGeyghksgxFCvRejVjBcfLc7e+ZeATbp7yvigXLPJ49o/RZCByRhhPUIQTlmiFRvLHYQ4HRXcZk43M80j6GVBIEW3tt1bgAw7Rc0M6s77pCO0m0If/GWKzy+Jk9BtLgADdW3M3hmUa6iCjJWSmBez8N8s+tK16PIqWoy7pKE= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727178924; c=relaxed/simple; bh=Bl2qzzEHgpGdJKV0zGc3PMz9DFh7mAtoqj4IPeX/p/Y=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=cemEHI05WC2X0zMmYeMA+HusW279Gjfhoos2TxS75i1P53+y+BXvr3+FubkHXv1t03XBIU6wdNSnUJiBjhqPonBqKDQTGeYgpHfJf8cl1iDptWxgegZ5shZxZU54d1qWJgeKXPeyzSu21iJ0NgjzX582B24OexjdxisuDuTVOLg= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org; spf=none smtp.mailfrom=linux-m68k.org; arc=none smtp.client-ip=195.130.132.52 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux-m68k.org Received: from ramsan.of.borg ([IPv6:2a02:1810:ac12:ed80:beb3:bbd4:b9cd:84ae]) by xavier.telenet-ops.be with cmsmtp id GBvL2D00N3rtkie01BvLdZ; Tue, 24 Sep 2024 13:55:21 +0200 Received: from rox.of.borg ([192.168.97.57]) by ramsan.of.borg with esmtp (Exim 4.95) (envelope-from ) id 1st48S-000Su2-Qp; Tue, 24 Sep 2024 13:55:20 +0200 Received: from geert by rox.of.borg with local (Exim 4.95) (envelope-from ) id 1st48W-005iAg-MA; Tue, 24 Sep 2024 13:55:20 +0200 From: Geert Uytterhoeven To: Kent Overstreet Cc: linux-bcachefs@vger.kernel.org, linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven Subject: [PATCH] bcachefs: BCACHEFS_PATH_TRACEPOINTS should depend on TRACING Date: Tue, 24 Sep 2024 13:55:15 +0200 Message-Id: X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" When tracing is disabled, there is no point in asking the user about enabling extra btree_path tracepoints in bcachefs. Fixes: 32ed4a620c5405be ("bcachefs: Btree path tracepoints") Signed-off-by: Geert Uytterhoeven --- fs/bcachefs/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/bcachefs/Kconfig b/fs/bcachefs/Kconfig index 5bac803ea367c034..e8549d04dcb8dd1b 100644 --- a/fs/bcachefs/Kconfig +++ b/fs/bcachefs/Kconfig @@ -89,7 +89,7 @@ config BCACHEFS_SIX_OPTIMISTIC_SPIN =20 config BCACHEFS_PATH_TRACEPOINTS bool "Extra btree_path tracepoints" - depends on BCACHEFS_FS + depends on BCACHEFS_FS && TRACING help Enable extra tracepoints for debugging btree_path operations; we don't normally want these enabled because they happen at very high rates. --=20 2.34.1