From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753482AbdK1Dqk (ORCPT ); Mon, 27 Nov 2017 22:46:40 -0500 Received: from mail.kernel.org ([198.145.29.99]:54646 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752516AbdK1Dqj (ORCPT ); Mon, 27 Nov 2017 22:46:39 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5CE8E218DA Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Mon, 27 Nov 2017 22:46:36 -0500 From: Steven Rostedt To: Masanari Iida Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH] linux-next: ftrace/docs: Fix spelling typos in ftrace-users.rst Message-ID: <20171127224636.7c0850d3@gandalf.local.home> In-Reply-To: <20171128032613.28315-1-standby24x7@gmail.com> References: <20171128032613.28315-1-standby24x7@gmail.com> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 28 Nov 2017 12:26:13 +0900 Masanari Iida wrote: > This patch corrects some spelling typo in ftrace-users.rst > > Signed-off-by: Masanari Iida > --- > Documentation/trace/ftrace-uses.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/trace/ftrace-uses.rst b/Documentation/trace/ftrace-uses.rst > index 8494a801d341..9df5ee15859a 100644 > --- a/Documentation/trace/ftrace-uses.rst > +++ b/Documentation/trace/ftrace-uses.rst > @@ -12,7 +12,7 @@ Written for: 4.14 > Introduction > ============ > > -The ftrace infrastructure was originially created to attach callbacks to the > +The ftrace infrastructure was originally created to attach callbacks to the > beginning of functions in order to record and trace the flow of the kernel. > But callbacks to the start of a function can have other use cases. Either > for live kernel patching, or for security monitoring. This document describes > @@ -29,7 +29,7 @@ going to idle, during CPU bring up and takedown, or going to user space. > This requires extra care to what can be done inside a callback. A callback > can be called outside the protective scope of RCU. > > -The ftrace infrastructure has some protections agains recursions and RCU > +The ftrace infrastructure has some protections against recursions and RCU > but one must still be very careful how they use the callbacks. > > Acked-by: Steven Rostedt (VMware) -- Steve