Re: [PATCH] h8300 thread flags cleanup

[Yoshinori Sato]

At Mon, 23 Nov 2009 18:20:32 -0500,
Mathieu Desnoyers wrote:
> 
> 2.6.32-rc introduces incoherent coding style in thread_info.h. Make sure
> the same style is used everywhere. Using style found in x86.
> 
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
> CC: Yoshinori Sato <ysato@xxxxxxxxxxxxxxxxxxxx>

Merged.
Thanks.

> ---
>  arch/h8300/include/asm/thread_info.h |   12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> Index: linux-2.6-lttng/arch/h8300/include/asm/thread_info.h
> ===================================================================
> --- linux-2.6-lttng.orig/arch/h8300/include/asm/thread_info.h	2009-11-22 20:42:35.000000000 -0500
> +++ linux-2.6-lttng/arch/h8300/include/asm/thread_info.h	2009-11-22 20:42:53.000000000 -0500
> @@ -93,13 +93,13 @@ static inline struct thread_info *curren
>  #define TIF_FREEZE		16	/* is freezing for suspend */
>  
>  /* as above, but as bit values */
> -#define _TIF_SYSCALL_TRACE	(1<<TIF_SYSCALL_TRACE)
> -#define _TIF_SIGPENDING		(1<<TIF_SIGPENDING)
> -#define _TIF_NEED_RESCHED	(1<<TIF_NEED_RESCHED)
> -#define _TIF_POLLING_NRFLAG	(1<<TIF_POLLING_NRFLAG)
> -#define _TIF_RESTORE_SIGMASK	(1<<TIF_RESTORE_SIGMASK)
> +#define _TIF_SYSCALL_TRACE	(1 << TIF_SYSCALL_TRACE)
> +#define _TIF_SIGPENDING		(1 << TIF_SIGPENDING)
> +#define _TIF_NEED_RESCHED	(1 << TIF_NEED_RESCHED)
> +#define _TIF_POLLING_NRFLAG	(1 << TIF_POLLING_NRFLAG)
> +#define _TIF_RESTORE_SIGMASK	(1 << TIF_RESTORE_SIGMASK)
>  #define _TIF_NOTIFY_RESUME	(1 << TIF_NOTIFY_RESUME)
> -#define _TIF_FREEZE		(1<<TIF_FREEZE)
> +#define _TIF_FREEZE		(1 << TIF_FREEZE)
>  
>  #define _TIF_WORK_MASK		0x0000FFFE	/* work to do on interrupt/exception return */
>  
> 
> -- 
> Mathieu Desnoyers
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

-- 
Yoshinori Sato
<ysato@xxxxxxxxxxxxxxxxxxxx>
--
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/