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 19:07:29 -0700 [thread overview]
Message-ID: <524F7461.4010703@roeck-us.net> (raw)
In-Reply-To: <CAOesGMj_DoC4iHsTMdbZ4sSOkbt-6nhaQgyFxtdvN96gXxyaxg@mail.gmail.com>
On 10/04/2013 10:04 AM, Olof Johansson wrote:
> On Fri, Oct 4, 2013 at 6:44 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>> 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 ?
>
> My buildbot scripts are some pretty ugly hacks that I don't
> particularly feel like publishing to the world. I can send you a copy
> though.
>
Not much different to the quality of mine :). Would be great if you can send me a copy.
For my scripts, I still have some secrets in there like my gmail password
in the clear. I'll have to make sure it is removed before I can publish it.
> The builder is one single beefy machine that i have on loan. It
> wouldn't be hard to make it distributed instead though; I've toyed
> around with prototypes for that in the past.
>
I would love to have something like that .. mine essentially consists
of four PCs with quad-core CPUs, plus two smaller systems which are
not always online.
Thanks,
Guenter
next prev parent reply other threads:[~2013-10-05 2:07 UTC|newest]
Thread overview: 19+ 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
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 [this message]
2013-10-04 10:28 ` Mark Brown
2013-10-04 19:45 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2025-10-03 12:08 Mark Brown
2024-10-03 3:53 Stephen Rothwell
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=524F7461.4010703@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.