From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Oct 10
Date: Fri, 11 Oct 2013 09:04:17 -0700 [thread overview]
Message-ID: <52582181.50901@roeck-us.net> (raw)
In-Reply-To: <20131010225507.GY21581@sirena.org.uk>
On 10/10/2013 03:55 PM, Mark Brown wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131010 tag is also provided for convenience.
>
> There were a few new conflicts which have been reported, each merge
> builds fine with x86 allmodconfig. A few cross tree integration fixes
> are still being carried but nothing new.
>
Build test results:
total: 110 pass: 97 skipped: 4 fail: 9
Failed builds:
arm:allmodconfig
arm:kirkwood_defconfig
blackfin:defconfig
mips:nlm_xlp_defconfig
mips:cavium_octeon_defconfig
powerpc:ppc64e_defconfig
powerpc:chroma_defconfig
powerpc:mpc85xx_smp_defconfig
sparc64:allmodconfig
mips qemu runs also still fail (and have for a while). mips32 hangs during boot, mips64 fails to build.
Details are at http://server.roeck-us.net:8010/builders.
For some reason buildbot fails to poll the repository status from gitorious. ZZManual update works, though.
I tried both git: and https: URLs. If anyone has an idea how to solve this problem, please let me know.
Thanks,
Guenter
next prev parent reply other threads:[~2013-10-11 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 22:55 linux-next: Tree for Oct 10 Mark Brown
2013-10-11 16:04 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-10 5:32 Stephen Rothwell
2022-10-10 4:47 Stephen Rothwell
2019-10-10 6:00 Stephen Rothwell
2018-10-10 5:46 Stephen Rothwell
2018-10-10 13:38 ` Guenter Roeck
2016-10-10 4:14 Stephen Rothwell
2014-10-10 5:56 Stephen Rothwell
2012-10-10 5:09 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=52582181.50901@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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).