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]

Date:	Mon, 28 Nov 2011 11:30:56 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
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

On Mon, 28 Nov 2011 13:53:17 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Dave,
> 
> 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.

Whatever. I'm onto it, but I think blocking -next merges for staging
breakage is broken to the point that -next needs fixing, or we should
kill staging off.

Alan
--
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/