From: Guenter Roeck <linux@roeck-us.net>
To: Olof Johansson <olof@lixom.net>
Cc: Mark Brown <broonie@kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 3
Date: Fri, 04 Oct 2013 06:44:56 -0700 [thread overview]
Message-ID: <524EC658.90706@roeck-us.net> (raw)
In-Reply-To: <CAOesGMhc5WYRFcBVSHShg6h8hn4HueGZtGCFKkzfX4SQEe_5LQ@mail.gmail.com>
On 10/03/2013 10:41 PM, Olof Johansson wrote:
> On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> On 10/03/2013 06:02 PM, Mark Brown wrote:
>>>
>>> Hi all,
>>>
>>> Better late than never 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-20131003 tag is also provided for convenience.
>>>
>>> A few new conflicts today caused by the removal of the h8300
>>> architecture which I didn't report for triviality. Several new build
>>> failures were found as a result of running allmodconfig tests between
>>> merges all of which have been reported and I'm still carrying the i.MX
>>> fix that Thierry has been carrying.
>>>
>>> Due to the length of time taken to run all the allmodconfigs I skipped
>>> the defconfig tests; I know Olof has the ARM stuff covered in his
>>> autobuilder. I'm going to use allyesconfig tomorrow since that should
>>> run faster so hopefully I can cover the ARM, i386 and x86_64 configs
>>> again.
>>>
>>
>> I could try to set up the buildbot farm I am using for -stable candidates
>> to also test the -next tree. Would that help ?
>
> ARM is pretty well-covered by my builds, I post results at:
>
> http://lists.linaro.org/mailman/listinfo/kernel-build-reports
>
Great summaries. Do you have a single builder, or several builders and
collect the results ? Either case, any chance sharing the buildbot scripts ?
Thanks,
Guenter
next prev parent reply other threads:[~2013-10-04 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 1:02 linux-next: Tree for Oct 3 Mark Brown
2013-10-04 5:23 ` Guenter Roeck
2013-10-04 5:41 ` Olof Johansson
2013-10-04 13:44 ` Guenter Roeck [this message]
2013-10-04 14:34 ` Mark Brown
2013-10-04 17:00 ` Olof Johansson
2013-10-04 17:52 ` Guenter Roeck
2013-10-04 17:04 ` Olof Johansson
2013-10-05 2:07 ` Guenter Roeck
2013-10-04 10:28 ` Mark Brown
2013-10-04 19:45 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 3:33 Stephen Rothwell
2019-10-03 4:34 Stephen Rothwell
2018-10-03 11:39 Stephen Rothwell
2016-10-03 4:19 Stephen Rothwell
2014-10-03 7:56 Stephen Rothwell
2012-10-03 7:30 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=524EC658.90706@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=olof@lixom.net \
--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).