linux-kernel - Re: [PATCH 10/35] Disintegrate asm/system.h for Hexagon [ver #2]

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]

Date:	Tue, 13 Mar 2012 11:31:02 -0500
From:	Richard Kuo <rkuo@...eaurora.org>
To:	David Howells <dhowells@...hat.com>
Cc:	Arnd Bergmann <arnd@...db.de>, paul.gortmaker@...driver.com,
	hpa@...or.com, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	linux-hexagon@...r.kernel.org
Subject: Re: [PATCH 10/35] Disintegrate asm/system.h for Hexagon [ver #2]

On Tue, Mar 13, 2012 at 10:01:40AM +0000, David Howells wrote:
> Arnd Bergmann <arnd@...db.de> wrote:
> 
> > Looking at this example, it could easily use the asm-generic versions of
> > switch_to.h and barrier.h, but that would complicate the dependency chain
> > again.
> 
> Yep.  The plan is to throw more patches on to the end of the series to
> consolidate those.
> 
> In fact, I wonder if we still really need the switch_to() macro wrapper, or
> whether we could replace it with an function, inline or otherwise, that
> returns the macro's third argument.
> 

Alrighty...  well, let me test this patch as is, and if I can, I'll see if
I can change over to the generic versions of switch_to.h and barrier.h as
well.


Thanks,
Richard Kuo


-- 

Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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/