From: rkuo <rkuo@codeaurora.org>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: linux-hexagon@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] arch: hexagon: kernel: hexagon_ksyms.c: export related symbols which various modules need
Date: Fri, 6 Dec 2013 12:25:02 -0600 [thread overview]
Message-ID: <20131206182502.GF11490@codeaurora.org> (raw)
In-Reply-To: <529DCE06.3040508@gmail.com>
On Tue, Dec 03, 2013 at 08:26:46PM +0800, Chen Gang wrote:
> Need export all related functions and symbols for various modules with
> allmodconfig. The related errors:
>
> MODPOST 2879 modules
> ERROR: "__vmyield" [sound/sound_firmware.ko] undefined!
> ERROR: "__phys_offset" [sound/drivers/snd-dummy.ko] undefined!
> ERROR: "ioremap_nocache" [drivers/char/ipmi/ipmi_si.ko] undefined!
> ERROR: "__iounmap" [drivers/char/ipmi/ipmi_si.ko] undefined!
> ...
>
> For including files, need "linux/*" first, then "asm/*". All related
> included files and symbols need be sorted by alphabetical order.
>
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> ---
> arch/hexagon/kernel/hexagon_ksyms.c | 24 ++++++++++++++++++++----
> 1 file changed, 20 insertions(+), 4 deletions(-)
>
OK, hopefully I didn't leave anything out, but I'll try to upstream the
patches with my tree hopefully in the next window. Thanks!
Acked-by: Richard Kuo <rkuo@codeaurora.org>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-12-06 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 4:01 [PATCH v2] arch: hexagon: kernel: hexagon_ksyms.c: export related symbols which various modules need Chen Gang
2013-11-29 4:03 ` Chen Gang
[not found] ` <20131203011222.GA23175@codeaurora.org>
2013-12-03 12:26 ` [PATCH v3] " Chen Gang
2013-12-06 18:25 ` rkuo [this message]
2013-12-07 9:35 ` Chen Gang
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=20131206182502.GF11490@codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=gang.chen.5i5j@gmail.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.