lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120507203216.GC10521@merkur.ravnborg.org>
Date:	Mon, 7 May 2012 22:32:16 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Tony Luck <tony.luck@...el.com>
Subject: Re: [patch 18/18] task_allocator: Use config switches instead of
	magic defines

On Sat, May 05, 2012 at 03:05:48PM -0000, Thomas Gleixner wrote:
> Replace __HAVE_ARCH_TASK_ALLOCATOR and __HAVE_ARCH_THREAD_ALLOCATOR
> with proper config switches.
> 
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
> Cc: Sam Ravnborg <sam@...nborg.org>
> Cc: Tony Luck <tony.luck@...el.com>

> Index: tip/arch/sparc/include/asm/thread_info_32.h
> ===================================================================
> --- tip.orig/arch/sparc/include/asm/thread_info_32.h
> +++ tip/arch/sparc/include/asm/thread_info_32.h
> @@ -80,8 +80,6 @@ register struct thread_info *current_thr
>   */
>  #define THREAD_INFO_ORDER  1
>  
> -#define __HAVE_ARCH_THREAD_INFO_ALLOCATOR
> -
>  BTFIXUPDEF_CALL(struct thread_info *, alloc_thread_info_node, int)
>  #define alloc_thread_info_node(tsk, node) BTFIXUP_CALL(alloc_thread_info_node)(node)

On the sparc mailing list we have discussed to drop
support for sun4c - and decided to do so.
With sun4c dropped sparc32 will be able to use the
generic variant too.

I will take care to introduce the generic variant
when sparc32 is ready.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ