Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp1259535pxb; Wed, 16 Feb 2022 14:58:58 -0800 (PST) X-Google-Smtp-Source: ABdhPJwn5e0bpFJuZQ4vo8GJAKTXOs2jXT5Fi5/pNVNxDhNhSlWQrp9jMARd+rY1sFGI6HL+m1Kc X-Received: by 2002:aa7:cf06:0:b0:405:e0c8:8b5d with SMTP id a6-20020aa7cf06000000b00405e0c88b5dmr5248046edy.367.1645052338711; Wed, 16 Feb 2022 14:58:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645052338; cv=none; d=google.com; s=arc-20160816; b=Dl3E1yoMJx0/XwK5k4pcBSWh0X8wweqvBpqbBL4HWWiB07myp2viGUydgtyaByKvJP c1URp2ukXGSg2++cxsptVO5EK4YSIoTQivRivJgYr5mSH4m4QjXC2juhEajoFrYPKWJ7 +urPE74v7jVbjjfUC+jsGi2iRdXA1JiWjB7NEj1o4pAqXv9Km5P9TMzKwercpXZ4vLTi 73YxSfZ6261cOqiIqEyydXUfSQOC87Xi+9ZX5t8u58wvakXcSASE5O8nW2Y49tGfbgAZ 3jVJzyhzWJgZANXgGLAa2AJBVL8eSu5HXqWncaYyZYu4/yc7iX0AzekmlUE1QHREpURI Jl6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=rZgBn61pM0rud/wc1Qin2v38we2HVCLzk7f6qrmtk6U=; b=x1EwW1buYqZwmU1dQAlDm3nXnPEAzQLBsLaY66IQODESGGHKJpSRJ8EmTWM6dACaG1 SNz99GBQgNBDEmAtgWW4Bito7boZUg6iANon0XhV5fBB84ygqJbho1l8sLQJTxbGHZO0 0vz0T5LE7JcTc8D4tGECrWrZlnluD+A5WAbJ2mZ/qNlfSa/nA1kp+SenwFHPy4xgifg8 sQ/gqdlymsC5Di43/sucXLNiqJWSg3frARGS6rM5PqIikhAAChJvuuDqxVhx3lO5Dn/i T37adG4+pm1pzSvKMcCBIY155eoOzNM5pL97cDjHAStlPq+h0nN2NvHwEYPzUKZ9D2jd mGOA== ARC-Authentication-Results: i=1; mx.google.com; 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 nb1si650027ejc.652.2022.02.16.14.58.36; Wed, 16 Feb 2022 14:58:58 -0800 (PST) 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; 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 S234159AbiBPQzb (ORCPT + 99 others); Wed, 16 Feb 2022 11:55:31 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:41074 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234355AbiBPQzX (ORCPT ); Wed, 16 Feb 2022 11:55:23 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 05AE329410F for ; Wed, 16 Feb 2022 08:55:11 -0800 (PST) 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 A38D6B81F94 for ; Wed, 16 Feb 2022 16:55:09 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 10833C004E1; Wed, 16 Feb 2022 16:55:07 +0000 (UTC) Date: Wed, 16 Feb 2022 11:55:06 -0500 From: Steven Rostedt To: Oscar Shiang Cc: Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [PATCH] tracing: Fix inconsistent style of mini-HOWTO Message-ID: <20220216115506.790ee23e@gandalf.local.home> In-Reply-To: References: X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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, 17 Feb 2022 00:50:06 +0800 Oscar Shiang wrote: > Each description should start with a hyphen and a space. Insert > spaces to fix it. > I can take this, but there's a possibility that it will be reverted. The output of the README in the tracefs file is an API. That is, the content of the text is used to determine what version and what options of tracing is enabled. If something is scanning for the trace_clock or timestamp_mode lines, doing an exact match of the entire context, this could break that code. If there's any report of that happening (and we should look for anything that might do that), then this will need to be reverted. -- Steve > Signed-off-by: Oscar Shiang > --- > kernel/trace/trace.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c > index 7c2578efd..a0d10e949 100644 > --- a/kernel/trace/trace.c > +++ b/kernel/trace/trace.c > @@ -5458,7 +5458,7 @@ static const char readme_msg[] = > " error_log\t- error log for failed commands (that support it)\n" > " buffer_size_kb\t- view and modify size of per cpu buffer\n" > " buffer_total_size_kb - view total size of all cpu buffers\n\n" > - " trace_clock\t\t-change the clock used to order events\n" > + " trace_clock\t\t- change the clock used to order events\n" > " local: Per cpu clock but may not be synced across CPUs\n" > " global: Synced across CPUs but slows tracing down.\n" > " counter: Not a clock, but just an increment\n" > @@ -5467,7 +5467,7 @@ static const char readme_msg[] = > #ifdef CONFIG_X86_64 > " x86-tsc: TSC cycle counter\n" > #endif > - "\n timestamp_mode\t-view the mode used to timestamp events\n" > + "\n timestamp_mode\t- view the mode used to timestamp events\n" > " delta: Delta difference against a buffer-wide timestamp\n" > " absolute: Absolute (standalone) timestamp\n" > "\n trace_marker\t\t- Writes into this file writes into the kernel buffer\n" > -- > 2.25.1