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 X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA2A0C433DF for ; Mon, 1 Jun 2020 12:28:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 91CA120870 for ; Mon, 1 Jun 2020 12:28:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727772AbgFAM2V (ORCPT ); Mon, 1 Jun 2020 08:28:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:37186 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726340AbgFAM2K (ORCPT ); Mon, 1 Jun 2020 08:28:10 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0F61D20820; Mon, 1 Jun 2020 12:28:09 +0000 (UTC) Received: from rostedt by gandalf.local.home with local (Exim 4.93) (envelope-from ) id 1jfjY0-00277K-3S; Mon, 01 Jun 2020 08:28:08 -0400 Message-ID: <20200601122807.983148242@goodmis.org> User-Agent: quilt/0.66 Date: Mon, 01 Jun 2020 08:27:36 -0400 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Ingo Molnar , Andrew Morton , Tom Zanussi , Randy Dunlap Subject: [for-next][PATCH 07/12] tracing/doc: Fix typos in histogram-design.rst References: <20200601122729.727113609@goodmis.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "Steven Rostedt (VMware)" There's a few typos in the histogram-design.rst document that need need to be fixed. Cc: Tom Zanussi Acked-by: Randy Dunlap Signed-off-by: Steven Rostedt (VMware) --- Documentation/trace/histogram-design.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/trace/histogram-design.rst b/Documentation/trace/histogram-design.rst index c246753f0ffc..06f5c7e5f2ee 100644 --- a/Documentation/trace/histogram-design.rst +++ b/Documentation/trace/histogram-design.rst @@ -700,7 +700,7 @@ variable, as well as the referenced variable's size, type, and is_signed values. The VAR_REF field's .name is set to the name of the variable it references. If a variable reference was created using the explicit system.event.$var_ref notation, the hist_field's system and -event_name variabls are also set. +event_name variables are also set. So, in order to handle an event for the sched_switch histogram, because we have a reference to a variable on another histogram, we @@ -1445,7 +1445,7 @@ reference to the variable being tracked, in this case the $wakeup_lat variable. In order to perform the onmax() handler function, there also needs to be a variable that tracks the current maximum by getting updated whenever a new maximum is hit. In this case, we can see that -an autogenerated veriable named ' __max' has been created and is +an auto-generated variable named ' __max' has been created and is visible in the actions[].track_data.track_var variable. Finally, in the new 'save action variables' section, we can see that @@ -1611,7 +1611,7 @@ A couple special cases While the above covers the basics of the histogram internals, there are a couple of special cases that should be discussed, since they -tend to creae even more confusion. Those are field variables on other +tend to create even more confusion. Those are field variables on other histograms, and aliases, both described below through example tests using the hist_debug files. -- 2.26.2