linux-kernel - Re: [PATCH 2/2] 32-bit ABI: introduce ARCH_32BIT_OFF

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] [day] [month] [year] [list]

Message-ID: <37236912.quIluKB8iJ@wuerfel>
Date:	Tue, 29 Dec 2015 14:54:50 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Yury Norov <ynorov@...iumnetworks.com>
Cc:	cmetcalf@...hip.com, linux-arch@...r.kernel.org,
	linux-kernel@...r.kernel.org, klimov.linux@...il.com
Subject: Re: [PATCH 2/2] 32-bit ABI: introduce ARCH_32BIT_OFF_T config option

On Tuesday 29 December 2015 14:43:41 Yury Norov wrote:
> On Tue, Dec 29, 2015 at 12:02:33PM +0100, Arnd Bergmann wrote:
> > On Tuesday 29 December 2015 12:26:35 Yury Norov wrote:
> > 
> > Acked-by: Arnd Bergmann <arnd@...db.de>
> > 
> > Should we merge the two patches through my asm-generic tree now, or should
> > we keep them in the ilp32 series, any preferences?
> > 
> > I think either way works.
> > 
> >       Arnd
> 
> I'd prefer asm-generic tree because they are not related to ILP32 only.
> 

Ok, I'll add it there after collecting a few more Acks. Generally speaking I
prefer to keep asm-generic patches in whatever series depends on them, as
there are normally very few changes, but it makes sense to merge this one
regardless just to make sure no other dependencies get added in case someone
submits a new architecture port at the same time.

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