Re: linux-next: Tree for December 6 (pch_uart)

[Randy Dunlap]

On Mon, 6 Dec 2010 16:09:33 +0100 Zimny Lech wrote:

> Ave,
> 
> 2010/12/6 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>:
> > Hi all,
> >
> > [The mirroring on kernel.org is currently being slow, so this release may
> > not be available yet.]
> >
> > Changes since 20101203:
> >
> 
> Nothing new here, only known issues
> 
> Kernel: arch/x86/boot/bzImage is ready  (#5)
>   Building modules, stage 2.
>   MODPOST 314 modules
> ERROR: "dma_release_channel" [drivers/serial/pch_uart.ko] undefined!
> ERROR: "__dma_request_channel" [drivers/serial/pch_uart.ko] undefined!
> WARNING: modpost: Found 4 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> make[2]: *** [__modpost] Error 1
> make[1]: *** [modules] Error 2
> make: *** [sub-make] Error 2

Greg, are you going to merge the patch that I posted for this one?



> WARNING: modpost: Found 9 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>   GEN     .version
>   CHK     include/generated/compile.h
>   UPD     include/generated/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> drivers/built-in.o: In function `pch_uart_startup':
> pch_uart.c:(.text+0x102efc): undefined reference to `__dma_request_channel'
> pch_uart.c:(.text+0x102f46): undefined reference to `__dma_request_channel'
> pch_uart.c:(.text+0x103037): undefined reference to `dma_release_channel'
> drivers/built-in.o: In function `pch_uart_shutdown':
> pch_uart.c:(.text+0x103135): undefined reference to `dma_release_channel'
> pch_uart.c:(.text+0x103151): undefined reference to `dma_release_channel'
> make[1]: *** [.tmp_vmlinux1] Error 1
> make: *** [sub-make] Error 2
> 

same patch as above.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/