From: Guenter Roeck <linux@roeck-us.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Tree for Oct 23
Date: Wed, 23 Oct 2013 13:01:49 -0700 [thread overview]
Message-ID: <20131023200149.GA3519@roeck-us.net> (raw)
In-Reply-To: <1382541202-6614-1-git-send-email-treding@nvidia.com>
On Wed, Oct 23, 2013 at 05:13:22PM +0200, Thierry Reding 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-20131023 tag is also provided for convenience.
>
> No new conflicts. I've fixed various build failures, so 32-bit and 64-bit
> allmodconfigs build fine on x86. ARM and x86 default configurations also
> build fine. Most of the patches to fix the build failures have been sent
> to the respective maintainers.
>
Build test results are a bit better than yesterday:
total: 110 pass: 92 skipped: 4 fail: 14
For the qemu tests, the mips64 build still fails due to an unused variable
'usp' in arch/mips/include/asm/syscall.h, and the sh test crashes with
a NULL pointer access in ata_finalize_port_ops().
Detailed results are, as always, available at http://server.roeck-us.net:8010/builders.
Guenter
next prev parent reply other threads:[~2013-10-23 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 15:13 linux-next: Tree for Oct 23 Thierry Reding
2013-10-23 20:01 ` Guenter Roeck [this message]
2013-10-24 7:20 ` Sedat Dilek
2013-10-24 7:41 ` Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 5:58 Stephen Rothwell
2020-10-23 2:34 Stephen Rothwell
2019-10-23 4:55 Stephen Rothwell
2019-10-23 6:05 ` Shaokun Zhang
2019-10-23 6:44 ` Geert Uytterhoeven
2019-10-23 6:56 ` Randy Dunlap
2019-10-23 6:57 ` Shaokun Zhang
2019-10-23 15:46 ` Mark Salyzyn
2019-10-23 20:45 ` Stephen Rothwell
2014-10-23 4:21 Stephen Rothwell
2014-10-23 12:47 ` Stephen Rothwell
2012-10-23 4:19 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=20131023200149.GA3519@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).