From: Guenter Roeck <linux@roeck-us.net>
To: Thierry Reding <thierry.reding@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Tree for Oct 15
Date: Tue, 15 Oct 2013 22:21:27 -0700 [thread overview]
Message-ID: <525E2257.7030604@roeck-us.net> (raw)
In-Reply-To: <1381845763-10487-1-git-send-email-treding@nvidia.com>
On 10/15/2013 07:02 AM, 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-20131015 tag is also provided for convenience.
>
> Gained a new conflict, but nothing too exciting. x86 and ARM default
> configurations build fine. I've also used an x86 allmodconfig build to
> check for build errors. Mark fixed most of those in the trees that he
> created last Thursday and Friday, so I've cherry-picked them on top of
> the final merge. There was one new build failure in the staging tree
> that was trivial to fix so I added a patch to the tree as well.
>
This build does look much better than the previous ones. I 'only' get 12 build failures
out of 106 configurations. Worst are powerpc builds, with 7 out of 14 builds failed.
Details are at http://server.roeck-us.net:8010/builders; look for the 'next' column.
Guenter
next prev parent reply other threads:[~2013-10-16 5:21 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 14:02 linux-next: Tree for Oct 15 Thierry Reding
2013-10-15 14:02 ` linux-next: manual merge of the trivial tree Thierry Reding
2013-10-16 9:12 ` Jozsef Kadlecsik
2013-10-16 9:20 ` Jiri Kosina
2013-10-16 14:56 ` Pablo Neira Ayuso
2013-10-16 20:10 ` Jozsef Kadlecsik
2013-10-15 14:02 ` [PATCH] [media] staging: media: Fix build for iMON LIRC driver Thierry Reding
2013-10-16 7:03 ` Dan Carpenter
2013-10-16 14:12 ` Greg Kroah-Hartman
2013-10-15 19:50 ` linux-next: Tree for Oct 15 (usb gadget f_mass_storage and storage_common) Randy Dunlap
2013-10-15 22:43 ` linux-next: Tree for Oct 15 (asymmetric keys) Randy Dunlap
2013-10-16 15:52 ` Thierry Reding
2013-10-19 17:07 ` Randy Dunlap
2013-10-16 5:21 ` Guenter Roeck [this message]
2013-10-16 15:50 ` linux-next: Tree for Oct 15 Thierry Reding
2013-10-16 16:37 ` Guenter Roeck
2013-10-16 16:43 ` Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2021-10-15 10:06 Stephen Rothwell
2020-10-15 7:28 Stephen Rothwell
2019-10-15 5:16 Stephen Rothwell
2018-10-15 8:25 Stephen Rothwell
2018-10-15 18:26 ` Guenter Roeck
2018-10-15 20:12 ` Stephen Rothwell
2018-10-15 20:24 ` Stephen Rothwell
2018-10-15 22:13 ` Andrew Morton
2018-10-16 13:36 ` Mike Rapoport
2018-10-16 20:41 ` Stephen Rothwell
2018-10-15 20:35 ` Rob Herring
2018-10-15 21:18 ` Guenter Roeck
2018-10-15 21:48 ` Rob Herring
2018-10-15 22:10 ` Guenter Roeck
2018-10-15 22:13 ` Rob Herring
2018-10-15 22:28 ` Guenter Roeck
2018-10-15 22:34 ` Guenter Roeck
2018-10-15 22:52 ` Rob Herring
2018-10-16 1:00 ` Rob Herring
2018-10-16 1:34 ` David Miller
2018-10-15 19:39 ` Guenter Roeck
2018-10-15 20:33 ` Stephen Rothwell
2018-10-15 21:35 ` Guenter Roeck
2018-10-15 22:22 ` Guenter Roeck
2018-10-16 2:02 ` Stephen Rothwell
2018-10-16 2:19 ` Stephen Rothwell
2018-10-16 3:12 ` Benjamin Herrenschmidt
2015-10-15 7:51 Stephen Rothwell
2014-10-15 4:29 Stephen Rothwell
2012-10-15 2:41 Stephen Rothwell
2008-10-15 10:58 linux-next tree " 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=525E2257.7030604@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).