[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151001113642.GI12635@sirena.org.uk>
Date: Thu, 1 Oct 2015 12:36:42 +0100
From: Mark Brown <broonie@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>
Cc: arnd@...db.de, yury.norov@...il.com, agraf@...e.de,
linux-kernel@...r.kernel.org, klimov.linux@...il.com,
Yury Norov <ynorov@...iumnetworks.com>,
bamvor.zhangjian@...wei.com, apinski@...ium.com,
philipp.tomsich@...obroma-systems.com,
linux-arm-kernel@...ts.infradead.org,
christoph.muellner@...obroma-systems.com
Subject: Re: [PATCH v5 00/23] ILP32 for ARM64
On Thu, Oct 01, 2015 at 12:19:31PM +0100, Catalin Marinas wrote:
> On Wed, Sep 30, 2015 at 05:41:03PM +0100, Mark Brown wrote:
> > Indeed. On that subject there was some discussion at Linaro Connect
> > last week about work (being done outside Linaro, not sure how public it
> > is at this point) to pull together the current state of the art into a
> > Docker container image which people can use for benchmarking and as a
> > reference for how to pull things together. That should help with the
> > analysis, it'll at least make it easier for other people to reproduce
> > any benchmarking results.
> That's fine and I would welcome it. However, I'm definitely against
> using non-agreed ABI and further spreading such toolchains (or kernel
You might want to speak to some of your colleagues about that... in any
case I'll reply off list later today with information on the third party
working on this so you can get in touch, like I say I'm not sure how
public that work is at this point.
> patches; Linaro's tracking kernel has kept these patches for a long
> time, even though the ABI has been NAK'ed).
I know, I'm not thrilled about that either. :/
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists