[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170126054515.GI7836@lianli.shorne-pla.net>
Date: Thu, 26 Jan 2017 14:45:15 +0900
From: Stafford Horne <shorne@...il.com>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: linux@...ck-us.net, fengguang.wu@...el.com,
Stephen Rothwell <sfr@...b.auug.org.au>,
Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Jan 19
On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne wrote:
>
> [...]
>
> >
> > Are all of these builds using the tests from lkp-tests [0]?
>
> Not using any specific tests, other than compiling allmodconfig and
> defconfig.
>
> >
> > If so and no one is working on openrisc toolchain updates I will package up
> > a modern toolchain for the cdn [1] and send patches for lkp-test.
> >
> > If there is something else that needs to be done let me know.
> >
> > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
>
> If you could work with Tony (his email is at the bottom of the crosstool
> front page in [1]) to get the or32 binutils updated, that would be
> great. With all the arch currrently in linux, I pretty much have to
> just use what is available from kernel.org as prebuilts.
>
Thanks,
I will followup with Tony.
Powered by blists - more mailing lists