Message-ID: <4E440F6D.7020009@windriver.com>
Date:	Thu, 11 Aug 2011 13:20:45 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Mike Frysinger <vapier.adi@...il.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>, <mingo@...e.hu>,
	<linux-kernel@...r.kernel.org>, <akpm@...ux-foundation.org>,
	<linux-arch@...r.kernel.org>, <sfr@...b.auug.org.au>
Subject: Re: [RFC/PULL 00/11] introduce export.h; reduce module.h usage

On 11-08-11 01:15 PM, Mike Frysinger wrote:
> On Thu, Aug 11, 2011 at 09:10, Paul Gortmaker wrote:
>> On 11-08-11 12:34 AM, Mike Frysinger wrote:
>>> On Wed, Aug 10, 2011 at 15:09, Paul Gortmaker wrote:
>>>> Have you thought about getting at least one blackfin defconfig in
>>>> the linux-next build coverage?  Gives you a better chance of
>>>> having people see when they've broken it.
>>>
>>> all of the blackfin defconfigs get tested nightly in linux-next by an
>>> ADI build machine.  i just didnt have a chance to review the logs as i
>>> was traveling.
>>
>> That is good, but as you've noted, it isn't something that anyone
>> else can see when they are combing the normal linux-next build
>> results below looking to see if they broke anything.
>>
>> http://kisskb.ellerman.id.au/kisskb/branch/9/
> 
> ive never heard of this site before, and there doesnt appear to be any
> documentation on that site about it
> -mike

It is mentioned in the boilerplate text that Stephen puts in his
daily linux-next emails (copied below).  Note the text about
"always open to add more builds" -- that is what I had in mind
when suggesting you get blackfin added to -next coverage builds.

P.

--------------

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc
and sparc64 defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.

Below is a summary of the state of the merge.

We are up to 199 trees (counting Linus' and 28 trees of patches pending
for Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.

There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ .  Thanks to Frank Seidel.

--
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists