Re: [PATCH] [RESEND][TRIVIAL] treewide: fix occurrences of "the the "

From: Randy Dunlap
Date: Thu Oct 02 2014 - 16:00:46 EST


One more then I'm done.

Thanks.

On 10/02/14 12:24, Michael Opdenacker wrote:

> diff --git a/arch/xtensa/kernel/entry.S b/arch/xtensa/kernel/entry.S
> index 82bbfa5a05b3..ccadbfd6645e 100644
> --- a/arch/xtensa/kernel/entry.S
> +++ b/arch/xtensa/kernel/entry.S
> @@ -384,7 +384,7 @@ common_exception:
> /* Save optional registers. */
>
> save_xtregs_opt a1 a2 a4 a5 a6 a7 PT_XTREGS_OPT
> -
> +
> #ifdef CONFIG_TRACE_IRQFLAGS
> l32i a4, a1, PT_DEPC
> /* Double exception means we came here with an exception
> @@ -433,7 +433,7 @@ common_exception_return:
> * We need to check some flags for signal handling and rescheduling,
> * and have to restore WB and WS, extra states, and all registers
> * in the register file that were in use in the user task.
> - * Note that we don't disable interrupts here.
> + * Note that we don't disable interrupts here.
> */
>
> _bbsi.l a4, TIF_NEED_RESCHED, 3f
> @@ -830,14 +830,14 @@ ENDPROC(unrecoverable_exception)
> * of the proper size instead.
> *
> * This algorithm simply backs out the register changes started by the user
> - * excpetion handler, makes it appear that we have started a window underflow
> + * exception handler, makes it appear that we have started a window underflow
> * by rotating the window back and then setting the old window base (OWB) in
> * the 'ps' register with the rolled back window base. The 'movsp' instruction
> * will be re-executed and this time since the next window frames is in the
> * active AR registers it won't cause an exception.
> *
> * If the WindowUnderflow code gets a TLB miss the page will get mapped
> - * the the partial windeowUnderflow will be handeled in the double exception
> + * and the partial windeowUnderflow will be handled in the double exception

windowUnderflow

> * handler.
> *
> * Entry condition:



--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/