From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stafford Horne <shorne@gmail.com>
Cc: linux@roeck-us.net, fengguang.wu@intel.com,
Stephen Rothwell <sfr@canb.auug.org.au>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 19
Date: Wed, 25 Jan 2017 11:37:11 -0500 [thread overview]
Message-ID: <20170125163711.GE29778@windriver.com> (raw)
In-Reply-To: <20170123141159.GE7836@lianli.shorne-pla.net>
[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.
Paul.
--
>
> -Stafford
next prev parent reply other threads:[~2017-01-25 16:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 5:39 linux-next: Tree for Jan 19 Stephen Rothwell
2017-01-19 16:42 ` Paul Gortmaker
2017-01-19 21:59 ` Stafford Horne
2017-01-23 14:11 ` Stafford Horne
2017-01-25 16:37 ` Paul Gortmaker [this message]
2017-01-26 4:54 ` Guenter Roeck
2017-01-26 5:38 ` Stafford Horne
2017-01-26 14:22 ` Guenter Roeck
2017-01-26 14:52 ` Paul Gortmaker
2017-01-26 5:45 ` Stafford Horne
2017-01-26 15:08 ` Stafford Horne
2017-01-26 16:19 ` Paul Gortmaker
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 1:51 Stephen Rothwell
2023-01-19 5:45 Stephen Rothwell
2021-01-19 7:03 Stephen Rothwell
2018-01-19 6:55 Stephen Rothwell
2016-01-19 3:11 Stephen Rothwell
2015-01-19 8:23 Stephen Rothwell
2012-01-19 1:59 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170125163711.GE29778@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).