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  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:	Tue, 23 Dec 2014 01:50:00 +0000
From:	Sid Boyce <>
To:	Paul Bolle <>,
	Linus Torvalds <>
CC:	"Nicholas A. Bellinger" <>,
	Jiri Kosina <>,
	Andrew Morton <>,
	Linux Kernel Mailing List <>,
	David Drysdale <>,
	Michal Marek <>
Subject: Re: Linux 3.19-rc1 - merge window closed

On 22/12/14 23:22, Paul Bolle wrote:
> On Mon, 2014-12-22 at 15:02 -0800, Linus Torvalds wrote:
>> Hmm. So it seems that there is something wrong with the dependency
>> generation for the generated header files. Possibly limited to just
>> the uapi files.
>> But I can't seem to recreate it even by trying to first build 3.18-rc2
>> and then switching to 3.19-rc1. So there's something
>> not-very-straightforward going on, possibly including some nasty race
>> in the Makefiles.
> The basically random build failure in
> might be related. Still makes no
> sense to me whatsoever.
> Paul Bolle
tindog:/usr/src/linux-3.19.0-rc1 # grep GM204_DISP_CORE_CHANNEL_DMA 
tindog:/usr/src/linux-3.19.0-rc1 #

Checking the other 2 boxes it's defined so I started with a fresh clone 
and it's now defined. As usual I did git pull on all 3 boxes to get from 
3.18.0 to 3.19-rc1.

tindog:/usr/src/linux # grep GM204_DISP_CORE_CHANNEL_DMA 
#define GM204_DISP_CORE_CHANNEL_DMA 0x0000957d

Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists