linux-kernel - Re: linux-next: build failure after merge of the drm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20111129001353.399142710ab77822b29552f0@canb.auug.org.au>
Date:	Tue, 29 Nov 2011 00:13:53 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Dave Airlie <airlied@...il.com>, Dave Airlie <airlied@...ux.ie>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: linux-next: build failure after merge of the drm tree

Hi Alan,

On Mon, 28 Nov 2011 11:30:56 +0000 Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>
> On Mon, 28 Nov 2011 13:53:17 +1100
> Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> > On Fri, 25 Nov 2011 10:34:19 +0000 Dave Airlie <airlied@...il.com> wrote:
> > >
> > > I just pushed jbarnes patch into my tree for now, at pushed out the
> > > mainline gma500 code with it.
> > 
> > And it is a mess (see my linux-next reports).
> 
> Well its very hard to sort stuff out when you are juggling a cross tree
> set of dependancies and someone pointlessly stops one of them being
> visible in next for ten days.

The mess in the drm tree has nothing to do with the staging tree.  It has
happened because the merge of your gms500 changes into the drm tree
interacted with other changes in that tree and the interactions were not
fixed in that tree.

You did read my error report from today, didn't you?  The build failure
was in drivers/gpu/drm/gma500/psb_drv.c.  The warnings indicating other
unfixed interactions were in drivers/gpu/drm/gma500/framebuffer.c.

As far as I can see, building the gma500 driver in the drm tree (on its
own) will fail.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped