Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 13 Nov 2019 14:55:19 -0500
From:   Steven Rostedt <rostedt@goodmis.org>
To:     "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
Cc:     tglx@linutronix.de, mingo@kernel.org, linux-kernel@vger.kernel.org,
        akaher@vmware.com, bordoloih@vmware.com, srivatsab@vmware.com,
        Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] Kconfig: Fix spelling mistake in user-visible help text
Message-ID: <20191113145519.161e9597@gandalf.local.home>
In-Reply-To: <157204450499.10518.4542293884417101528.stgit@srivatsa-ubuntu>
References: <157204450499.10518.4542293884417101528.stgit@srivatsa-ubuntu>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, 25 Oct 2019 16:02:07 -0700
"Srivatsa S. Bhat" <srivatsa@csail.mit.edu> wrote:

> From: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
> 
> Fix a spelling mistake in the help text for PREEMPT_RT.

I guess this should go in via the scheduler tree?

Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

-- Steve


> 
> Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
> ---
> 
>  kernel/Kconfig.preempt |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/Kconfig.preempt b/kernel/Kconfig.preempt
> index deff972..bf82259 100644
> --- a/kernel/Kconfig.preempt
> +++ b/kernel/Kconfig.preempt
> @@ -65,7 +65,7 @@ config PREEMPT_RT
>  	  preemptible priority-inheritance aware variants, enforcing
>  	  interrupt threading and introducing mechanisms to break up long
>  	  non-preemptible sections. This makes the kernel, except for very
> -	  low level and critical code pathes (entry code, scheduler, low
> +	  low level and critical code paths (entry code, scheduler, low
>  	  level interrupt handling) fully preemptible and brings most
>  	  execution contexts under scheduler control.
>