[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080418074736.GA27579@elte.hu>
Date: Fri, 18 Apr 2008 09:47:42 +0200
From: Ingo Molnar <mingo@...e.hu>
To: David Miller <davem@...emloft.net>
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
arjan@...radead.org
Subject: Re: [v2.6.26] what's brewing in x86.git for v2.6.26
* David Miller <davem@...emloft.net> wrote:
> From: Andrew Morton <akpm@...ux-foundation.org>
> Date: Thu, 17 Apr 2008 23:27:47 -0700
>
> > On Wed, 16 Apr 2008 22:23:38 +0200 Ingo Molnar <mingo@...e.hu> wrote:
> >
> > > Arjan van de Ven (6):
> > > ...
> > > x86: mark init_mm deprecated
> >
> > Why can't I find this patch on the mailing list?
> >
> > It's an MM patch which touches sched.h. It should not be in
> > git-x86. It generates over a megabyte of warnings on sparc64.
>
> If you're going to touch generic code, test build on other platforms
> or get it into a tree where such build testing is done for you.
we do an automatic build test (of both vmlinux and of modules) of over
80 non-x86 architecture configs, amongst them are sparc64 and sparc
configs:
http://www.tglx.de/autoqa-cgi/index?run=86&tree=1
for the latest version of our trees all the 80 non-x86 configs (and all
96 configs in total) built successfully.
if in the sparc64 row you click on the green "OK" button (which signals
that the build was successful) you can get the build log and see all 7
warnings that get triggered on the sparc64 defconfig with
sched-devel/latest [which embedds x86/latest].
so i'm not sure where those "over a megabyte of warnings" come from.
Ingo
--
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