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 5699AC61DA4 for ; Thu, 9 Feb 2023 11:42:25 +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:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=kwqQwHBTIcHtNjuuhqUE0bpzQ5rgXru7Ik7FeSfZqK0=; b=5ApBsdUYSWA9TX JgiCPnFVJjLwSua2U235k07qAEwQjPSh8For0pZ1VES3nG0vy8uwt/MTEpJFcAQvXwDjFfTAnGTss ox0CrRwzxv5QL/lMMFNsYJhicYi2hlqQtZq5oaoEqPYOYMTnW2/jQM1BhTaDWxgs+CbEVE6NfKU5T TEUcCdHIfEyDMnd9kVHSwMkg8WBNIYkm46o4xIzkG3V6zGuh73nhxG/GaY4Vl2p+R5LNMJHfvQWGp h+QUz9CcQSKti+DHUJFW4742qTGzuEqUpGXKl5U9caExdNK7YvvrXjmSnwn/nUQTehzyO51oErNKc q0Hr4KiPLjbQXh2swf+w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pQ5Ip-001M7x-2w; Thu, 09 Feb 2023 11:41:23 +0000 Received: from mail-pf1-x42c.google.com ([2607:f8b0:4864:20::42c]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pQ5Ia-001M6Q-MJ for linux-arm-kernel@lists.infradead.org; Thu, 09 Feb 2023 11:41:12 +0000 Received: by mail-pf1-x42c.google.com with SMTP id s20so1132000pfe.2 for ; Thu, 09 Feb 2023 03:41:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=yProl2BDwB5rM572Fbs59r3WL3B/5I59AVOYb+PuqHI=; b=KV/bOyz4S4KezQKKFVQaOOMbqOITttsXwy8iRe3FKzile+YMvQpsXjlrBt+eVKkIhA CllK54eqi+PV6eu/AEMwJMumk6EFiWmxtny2ybtbu/UOjns1koYHTZu1asp9C6lFsbQy WAhbQ6aqAIc4FpwbNIn1PlqSKdxo77osYJSDg1qZya+yEZubtT6zceSRDDH33l/Ri1yy YJyoEi/fg2vZJrRaDDIdYw51bT+f7JtWrqmntTTHlQUb0tNiRrurlXah2Qo/nJ/34GBY ZH4XsxYRhOyMWJy8WpweYPbg4q2oPvS3k5LwN8EGVTGsP6NJA46xcoNAM9SaNdDR00M4 zkzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=yProl2BDwB5rM572Fbs59r3WL3B/5I59AVOYb+PuqHI=; b=QwdncCJ8f6xRdjysajf8jQZLCn70xsObaCci6/zU2ot46EV19qwl7R4PItc00Zvibu t12NN+U+uNOLCQNJ1gnmcIfgBvy1QxRJRAs+mW7u8eoX390tOZYMqgPa6ax6G44NqUN/ RW36FQsv68Fh+q7xYEXj6T0hV4A5WKaSYWUvdVLYjlngLeIMhIJL0nSQCQG0SlNNvM2k Rkv/nH9/yAYiywubFZsyfrdDEtCBn+7wjmHCev5PPI9KE31PjOGs60xlUqUCTzAYJ8wk x7wjLBMBdGEmsGK+3aBO/MR8jsGsd7Li7EH4dUgKFm0Bo5CDHWos44ehpTUzjhNlLFzA SKEA== X-Gm-Message-State: AO0yUKX4zH/CNHncS6XG6HMsnjNeSAOv8GoJc0hS2kn76moxtrs+4URL wqgTjn8XAj0I3hoNgul5W8qU1gZhRFWQbo6e1zSx9A== X-Google-Smtp-Source: AK7set/plM8/DX1Q4MYjtoJGIq6qokxZinH6ULU+y7Qbmu93F1XvNHH+br2ZXCpqQjFfdJKMazyGqra/KUg2lQRnsNk= X-Received: by 2002:a62:2503:0:b0:5a8:494a:e498 with SMTP id l3-20020a622503000000b005a8494ae498mr913346pfl.51.1675942867561; Thu, 09 Feb 2023 03:41:07 -0800 (PST) MIME-Version: 1.0 References: <20230209071400.31476-1-rdunlap@infradead.org> <20230209071400.31476-22-rdunlap@infradead.org> In-Reply-To: <20230209071400.31476-22-rdunlap@infradead.org> From: Mike Leach Date: Thu, 9 Feb 2023 11:40:55 +0000 Message-ID: Subject: Re: [PATCH 21/24] Documentation: trace: correct spelling To: Randy Dunlap Cc: linux-kernel@vger.kernel.org, Steven Rostedt , Masami Hiramatsu , Daniel Bristot de Oliveira , linux-trace-kernel@vger.kernel.org, Mathieu Poirier , Suzuki K Poulose , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, Jonathan Corbet , linux-doc@vger.kernel.org, Mukesh Ojha X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230209_034108_820714_2E2EB29E X-CRM114-Status: GOOD ( 37.36 ) 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 Reviewed by: Mike Leach On Thu, 9 Feb 2023 at 07:14, Randy Dunlap wrote: > > Correct spelling problems for Documentation/trace/ as reported > by codespell. > > Signed-off-by: Randy Dunlap > Cc: Steven Rostedt > Cc: Masami Hiramatsu > Cc: Daniel Bristot de Oliveira > Cc: linux-trace-kernel@vger.kernel.org > Cc: Mathieu Poirier > Cc: Suzuki K Poulose > Cc: coresight@lists.linaro.org > Cc: linux-arm-kernel@lists.infradead.org > Cc: Jonathan Corbet > Cc: linux-doc@vger.kernel.org > Reviewed-by: Mukesh Ojha > Acked-by: Steven Rostedt (Google) > Acked-by: Suzuki K Poulose # for coresight > --- > Documentation/trace/coresight/coresight-etm4x-reference.rst | 2 +- > Documentation/trace/events.rst | 6 +++--- > Documentation/trace/fprobe.rst | 2 +- > Documentation/trace/ftrace-uses.rst | 2 +- > Documentation/trace/hwlat_detector.rst | 2 +- > Documentation/trace/uprobetracer.rst | 2 +- > 7 files changed, 9 insertions(+), 9 deletions(-) > > diff -- a/Documentation/trace/coresight/coresight-etm4x-reference.rst b/Documentation/trace/coresight/coresight-etm4x-reference.rst > --- a/Documentation/trace/coresight/coresight-etm4x-reference.rst > +++ b/Documentation/trace/coresight/coresight-etm4x-reference.rst > @@ -675,7 +675,7 @@ Bit assignments shown below:- > reconstructed using only conditional branches. > > There is currently no support in Perf for supplying modified binaries to the decoder, so this > - feature is only inteded to be used for debugging purposes or with a 3rd party tool. > + feature is only intended to be used for debugging purposes or with a 3rd party tool. > > Choosing this option will result in a significant increase in the amount of trace generated - > possible danger of overflows, or fewer instructions covered. Note, that this option also > diff -- a/Documentation/trace/events.rst b/Documentation/trace/events.rst > --- a/Documentation/trace/events.rst > +++ b/Documentation/trace/events.rst > @@ -903,7 +903,7 @@ functions can be used. > > To create a kprobe event, an empty or partially empty kprobe event > should first be created using kprobe_event_gen_cmd_start(). The name > -of the event and the probe location should be specfied along with one > +of the event and the probe location should be specified along with one > or args each representing a probe field should be supplied to this > function. Before calling kprobe_event_gen_cmd_start(), the user > should create and initialize a dynevent_cmd object using > @@ -983,7 +983,7 @@ The basic idea is simple and amounts to > layer that can be used to generate trace event commands. The > generated command strings can then be passed to the command-parsing > and event creation code that already exists in the trace event > -subystem for creating the corresponding trace events. > +subsystem for creating the corresponding trace events. > > In a nutshell, the way it works is that the higher-level interface > code creates a struct dynevent_cmd object, then uses a couple > @@ -1056,7 +1056,7 @@ to add an operator between the pair (her > appended onto the end of the arg pair (here ';'). > > There's also a dynevent_str_add() function that can be used to simply > -add a string as-is, with no spaces, delimeters, or arg check. > +add a string as-is, with no spaces, delimiters, or arg check. > > Any number of dynevent_*_add() calls can be made to build up the string > (until its length surpasses cmd->maxlen). When all the arguments have > diff -- a/Documentation/trace/fprobe.rst b/Documentation/trace/fprobe.rst > --- a/Documentation/trace/fprobe.rst > +++ b/Documentation/trace/fprobe.rst > @@ -111,7 +111,7 @@ saved at function entry and passed to ex > the instruction pointer of @regs may be different from the @entry_ip > in the entry_handler. If you need traced instruction pointer, you need > to use @entry_ip. On the other hand, in the exit_handler, the instruction > - pointer of @regs is set to the currect return address. > + pointer of @regs is set to the correct return address. > > Share the callbacks with kprobes > ================================ > diff -- a/Documentation/trace/ftrace-uses.rst b/Documentation/trace/ftrace-uses.rst > --- a/Documentation/trace/ftrace-uses.rst > +++ b/Documentation/trace/ftrace-uses.rst > @@ -193,7 +193,7 @@ FTRACE_OPS_FL_RECURSION > Not, if this flag is set, then the callback will always be called > with preemption disabled. If it is not set, then it is possible > (but not guaranteed) that the callback will be called in > - preemptable context. > + preemptible context. > > FTRACE_OPS_FL_IPMODIFY > Requires FTRACE_OPS_FL_SAVE_REGS set. If the callback is to "hijack" > diff -- a/Documentation/trace/hwlat_detector.rst b/Documentation/trace/hwlat_detector.rst > --- a/Documentation/trace/hwlat_detector.rst > +++ b/Documentation/trace/hwlat_detector.rst > @@ -14,7 +14,7 @@ originally written for use by the "RT" p > kernel is highly latency sensitive. > > SMIs are not serviced by the Linux kernel, which means that it does not > -even know that they are occuring. SMIs are instead set up by BIOS code > +even know that they are occurring. SMIs are instead set up by BIOS code > and are serviced by BIOS code, usually for "critical" events such as > management of thermal sensors and fans. Sometimes though, SMIs are used for > other tasks and those tasks can spend an inordinate amount of time in the > diff -- a/Documentation/trace/uprobetracer.rst b/Documentation/trace/uprobetracer.rst > --- a/Documentation/trace/uprobetracer.rst > +++ b/Documentation/trace/uprobetracer.rst > @@ -55,7 +55,7 @@ Synopsis of uprobe_tracer > > (\*1) only for return probe. > (\*2) this is useful for fetching a field of data structures. > - (\*3) Unlike kprobe event, "u" prefix will just be ignored, becuse uprobe > + (\*3) Unlike kprobe event, "u" prefix will just be ignored, because uprobe > events can access only user-space memory. > > Types > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- Mike Leach Principal Engineer, ARM Ltd. Manchester Design Centre. UK _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel