Re: Build errors in stable queue (3.10, 3.14, 3.16)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 24, 2014 at 06:11:38AM -0700, Guenter Roeck wrote:
> On 10/23/2014 11:23 PM, Greg Kroah-Hartman wrote:
> >On Thu, Oct 23, 2014 at 11:11:46PM -0700, Guenter Roeck wrote:
> >>Several arm targets are affected.
> >>
> >>drivers/dma/pl330.c: In function 'pl330_probe':
> >>drivers/dma/pl330.c:3054:10: error: 'struct dma_pl330_chan' has no member named 'thread'
> >>drivers/dma/pl330.c: In function 'pl330_remove':
> >>drivers/dma/pl330.c:3087:10: error: 'struct dma_pl330_chan' has no member named 'thread'
> >>make[2]: *** [drivers/dma/pl330.o] Error 1
> >>
> >>Error is always the same for 3.10, 3,14, and 3.16.
> >
> >Thanks, I'll go delete the patch that causes this problem, and hope the
> >developers will resend a fix for it.
> >
> 
> Now pretty much everything fails to build in 3.16.
> 
> 
> mm/migrate.c: In function '__unmap_and_move':
> mm/migrate.c:932:13: error: 'MIGRATEPAGE_BALLOON_SUCCESS' undeclared (first use in this function)
> mm/migrate.c:932:13: note: each undeclared identifier is reported only once for each function it appears in
> make[1]: *** [mm/migrate.o] Error 1

Odd, I can't duplicate this one.

> and some in 3.14.
> 
> Error log:
> security/integrity/ima/ima_crypto.c: In function 'ima_kernel_read':
> security/integrity/ima/ima_crypto.c:52:21: error: 'const struct file_operations' has no member named 'read_iter'
> security/integrity/ima/ima_crypto.c:53:3: error: implicit declaration of function 'new_sync_read' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> make[3]: *** [security/integrity/ima/ima_crypto.o] Error 1

This is now fixed.

> 3.10 still has above failure, plus
> 
> {standard input}: Assembler messages:
> {standard input}:51: Error: operands mismatch -- statement `move.b %a1,(%a0)' ignored
> make[1]: *** [arch/m68k/lib/uaccess.o] Error 1
> 
> in the m68k build. No idea how that happened.

I have no idea what happened here.

I've just pushed out updated trees, can you see if they cause problems
for you?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]