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] [day] [month] [year] [list]
Date:	Sun, 17 Jul 2011 11:13:21 +0200
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Alan Cox <alan@...ux.intel.com>
Subject: Re: linux-next: build failure after merge of the staging tree

On Sat, Jul 16, 2011 at 11:18:00PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> In file included from drivers/staging/gma500/backlight.c:23:0:
> drivers/staging/gma500/psb_drv.h:34:22: fatal error: medfield.h: No such file or directory
> In file included from drivers/staging/gma500/accel_2d.c:39:0:
> drivers/staging/gma500/psb_drv.h:34:22: fatal error: medfield.h: No such file or directory
> In file included from drivers/staging/gma500/gem.c:29:0:
> drivers/staging/gma500/psb_drv.h:34:22: fatal error: medfield.h: No such file or directory
> In file included from drivers/staging/gma500/framebuffer.c:36:0:
> drivers/staging/gma500/psb_drv.h:34:22: fatal error: medfield.h: No such file or directory
> In file included from drivers/staging/gma500/gtt.c:23:0:
> drivers/staging/gma500/psb_drv.h:34:22: fatal error: medfield.h: No such file or directory
> In file included from drivers/staging/gma500/intel_bios.c:24:0:
> drivers/staging/gma500/psb_drv.h:34:22: fatal error: medfield.h: No such file or directory
> 
> Caused by commit 3caa89e93364 ("gma500: resync with Medfield progress").
> 
> I have used the staging tree from next-20110707 for today.

This should now be fixed.

thanks,

greg k-h
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ