From: Mark Brown <broonie@kernel•org>
To: Guenter Roeck <linux@roeck-us•net>
Cc: linux-next@vger•kernel.org,
Thierry Reding <thierry.reding@gmail•com>,
linux-kernel@vger•kernel.org, Olof Johansson <olof@lixom•net>
Subject: Re: linux-next: Tree for Oct 3
Date: Fri, 4 Oct 2013 11:28:39 +0100 [thread overview]
Message-ID: <20131004102839.GJ27287@sirena.org.uk> (raw)
In-Reply-To: <524E50DB.3060707@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
On Thu, Oct 03, 2013 at 10:23:39PM -0700, Guenter Roeck wrote:
> On 10/03/2013 06:02 PM, Mark Brown wrote:
> >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 ?
Yes, that'd be great. Like Olof said ARM is pretty well covered but
adding more platforms would be very helpful.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-04 10:29 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
2013-10-04 10:28 ` Mark Brown [this message]
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=20131004102839.GJ27287@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=olof@lixom$(echo .)net \
--cc=thierry.reding@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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