From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Announce: rmk's nightly builder gets ARM64 support
Date: Thu, 19 Feb 2015 17:12:20 +0000 [thread overview]
Message-ID: <20150219171220.GA8656@n2100.arm.linux.org.uk> (raw)
Today, I have added ARM64 support to my automated nightly kernel builder.
Initially, this will result in ARM64 builds being tested with allnoconfig
and defconfig, and I shall add allmodconfig and allyesconfig to this in
the coming days.
Once that is done and stable, I will investigate adding an ARM Juno
platform to my boot farm so we can run the results of the builder.
Other recent changes have been a disk upgrade, so the builder now has
plenty of disk space to run the allmodconfig and allyesconfig, which
used to fail (or be skipped) when the disk space was low.
I've also added a new ARM target for building the defconfig without a
seed.
As ever, all results are in the usual place, at:
http://www.arm.linux.org.uk/developer/build/
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next reply other threads:[~2015-02-19 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 17:12 Russell King - ARM Linux [this message]
2015-02-19 18:34 ` Announce: rmk's nightly builder gets ARM64 support Russell King - ARM Linux
2015-02-20 9:20 ` Will Deacon
2015-02-20 9:24 ` Ard Biesheuvel
2015-02-20 9:40 ` Russell King - ARM Linux
2015-02-20 10:20 ` Russell King - ARM Linux
2015-02-20 10:35 ` Fabio Estevam
2015-02-20 13:38 ` Russell King - ARM Linux
2015-02-20 13:49 ` Fabio Estevam
2015-02-20 14:03 ` Ard Biesheuvel
2015-02-20 14:04 ` Will Deacon
2015-02-20 17:59 ` Russell King - ARM Linux
2015-02-20 18:02 ` Fabio Estevam
2015-02-20 18:08 ` Marc Zyngier
2015-02-20 18:32 ` Will Deacon
2015-02-20 22:12 ` Rob Herring
2015-02-20 19:03 ` Robert Schwebel
2015-02-20 11:45 ` Jeremy Kerr
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=20150219171220.GA8656@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).