From: Guenter Roeck <linux@roeck-us.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Frysinger <vapier@gentoo.org>,
Ingo Molnar <mingo@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH v2] early_printk: consolidate random copies of identical code
Date: Fri, 8 Mar 2013 07:29:34 -0800 [thread overview]
Message-ID: <20130308152934.GA18274@roeck-us.net> (raw)
In-Reply-To: <20130308011042.GE9161@home.goodmis.org>
On Thu, Mar 07, 2013 at 08:10:43PM -0500, Steven Rostedt wrote:
> On Thu, Mar 07, 2013 at 07:49:35PM -0500, Paul Gortmaker wrote:
> >
> > Within an hour, Fengguang's robots[1] found the branch, were compiling
> > it for fringe architectures, and running sparse on it, and sending me the
> > sparse regressions. I'd listened to Fengguang's presentation while at
> > KS in San Diego, but I had no idea it was this proactive, until it did
> > autobot testing on my branch.
>
> And people wonder why I wanted to give Fengguang a round of applauds
> there. I guess I was one of the first people to get his testing, as it
> found a lot of little things for me that my own tests missed.
>
> >
> > I have most of the prebuilt toolchains[2], and two line wrappers to set
> > the ARCH/CROSS_COMPILE, but as it stands, it seems I really don't
> > need those any more. I can sanity test on a common arch and then
> > simply push to kernel.org to trigger build sanity across all arch. I'll
> > probably still continue to use the toolchain prebuilts to test locally
> > though, just for the peace of mind. But knowing FW bots are doing
> > testing before it goes into linux-next or anywhere else is really nice.
> >
>
> I should stress that there's a sample ktest.pl file for everyone:
>
> tools/testing/ktest/examples/crosstests.conf
>
> Just download the cross compilers from:
>
> (assuming you're running on an x86_64 box)
>
> https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/
>
Have you tried that link recently ?
I get:
Forbidden
You don't have permission to access /pub/tools/crosstool/files/bin/x86_64/4.6.3/
on this server.
Guenter
next prev parent reply other threads:[~2013-03-08 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 19:15 [PATCH v2] early_printk: consolidate random copies of identical code Paul Gortmaker
2013-03-07 19:25 ` Andrew Morton
2013-03-07 19:50 ` Paul Gortmaker
2013-03-07 20:05 ` Joe Perches
2013-03-07 21:35 ` Andrew Morton
2013-03-07 21:41 ` Thomas Gleixner
2013-03-07 22:47 ` Rob Landley
2013-03-08 0:49 ` Paul Gortmaker
2013-03-08 0:56 ` Andrew Morton
2013-03-08 1:15 ` Paul Gortmaker
2013-03-08 1:10 ` Steven Rostedt
2013-03-08 15:29 ` Guenter Roeck [this message]
2013-03-07 20:20 ` Paul Gortmaker
2013-03-07 21:25 ` Thomas Gleixner
2013-03-07 21:43 ` Andrew Morton
2013-03-07 22:34 ` Thomas Gleixner
2013-03-08 16:11 ` [PATCH v3] " Paul Gortmaker
2013-03-08 21:46 ` Andrew Morton
2013-03-23 21:23 ` Geert Uytterhoeven
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=20130308152934.GA18274@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vapier@gentoo.org \
/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