public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle•com>
To: Zimny Lech <napohybelskurwysynom2010@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for December 6 (pch_uart)
Date: Mon, 6 Dec 2010 08:14:22 -0800	[thread overview]
Message-ID: <20101206081422.0608c50d.randy.dunlap@oracle.com> (raw)
In-Reply-To: <AANLkTi=iCZ=XQk3zXwK-BPnK4=9SU5W-arf+rom9dx8V@mail.gmail.com>

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

> Ave,
> 
> 2010/12/6 Stephen Rothwell <sfr@canb•auug.org.au>:
> > 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 ***

  reply	other threads:[~2010-12-06 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06  3:00 linux-next: Tree for December 6 Stephen Rothwell
2010-12-06 15:09 ` Zimny Lech
2010-12-06 16:14   ` Randy Dunlap [this message]
2010-12-10 17:20     ` linux-next: Tree for December 6 (pch_uart) Randy Dunlap
2010-12-10 23:16       ` Greg KH
2010-12-07 10:23 ` linux-next: Tree for December 6 Zimny Lech
2010-12-07 18:38   ` [PATCH -next] media: fix em28xx build, needs interrupt.h Randy Dunlap
2010-12-07 18:44     ` Alexey Dobriyan
2010-12-07 18:50       ` [PATCH -next v2] media: fix em28xx build, needs hardirq.h Randy Dunlap
2010-12-16 18:03         ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101206081422.0608c50d.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=napohybelskurwysynom2010@gmail$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox