linux-kernel - Re: [PATCH] x86: unify appropriate bits from dumpstack_32 and dumpstack

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081027182148.GL3046@elte.hu>
Date:	Mon, 27 Oct 2008 19:21:48 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Alexander van Heukelum <heukelum@...tmail.fm>
Cc:	Neil Horman <nhorman@...driver.com>, linux-kernel@...r.kernel.org,
	Alexander van Heukelum <heukelum@...lshack.com>,
	Thomas Gleixner <tglx@...utronix.de>, mingo@...hat.com,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] x86: unify appropriate bits from dumpstack_32 and
	dumpstack_64


* Alexander van Heukelum <heukelum@...tmail.fm> wrote:

> On Thu, 23 Oct 2008 10:40:06 -0400, "Neil Horman"
> <nhorman@...driver.com> said:
> > Hey all-
> > 	As promised, now that dumpstack_32 and dumpstack_64 have so many bits in
> > common, we should merge the in-sync bits into a common file, to prevent them
> > from diverging again.  This patch removes bits which are common between
> > dumpstack_32.c and dumpstack_64.c and places them in a common dumpstack.c
> > which is built for both 32 and 64 bit arches.  
> > 
> > Regards
> > Neil
> > 
> > Signed-off-by: Neil Horman <nhorman@...driver.com>
> 
> A bit late, maybe, but if it matters:
> 
> Acked-by: Alexander van Heukelum <heukelum@...tmail.fm>

i've updated the commit, thanks.

	Ingo
--
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/