linux-hexagon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Richard Kuo <rkuo@codeaurora.org>
Cc: linux-hexagon@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arch: hexagon: kernel: hexagon_ksyms.c: export related symbols which various modules need
Date: Fri, 29 Nov 2013 12:03:46 +0800	[thread overview]
Message-ID: <52981222.3080007@gmail.com> (raw)
In-Reply-To: <529811AE.8050502@gmail.com>


After this patch, excluding the VGA_CONSOLE issue, the hexagon can pass
allmodconfig. :-)

Please help check all related patches when you have time.


Thanks.

On 11/29/2013 12:01 PM, 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!
>   ...
> 
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> ---
>  arch/hexagon/kernel/hexagon_ksyms.c |   27 +++++++++++++++++++++++----
>  1 files changed, 23 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/hexagon/kernel/hexagon_ksyms.c b/arch/hexagon/kernel/hexagon_ksyms.c
> index 32b1379..3188de4 100644
> --- a/arch/hexagon/kernel/hexagon_ksyms.c
> +++ b/arch/hexagon/kernel/hexagon_ksyms.c
> @@ -20,6 +20,9 @@
>  
>  #include <asm/hexagon_vm.h>
>  #include <asm/uaccess.h>
> +#include <asm/io.h>
> +#include <linux/dma-mapping.h>
> +#include <asm/dma-mapping.h>
>  
>  EXPORT_SYMBOL(__copy_from_user_hexagon);
>  EXPORT_SYMBOL(__copy_to_user_hexagon);
> @@ -28,13 +31,29 @@ EXPORT_SYMBOL(__vmsetie);
>  EXPORT_SYMBOL(memcpy);
>  EXPORT_SYMBOL(memset);
>  
> +/* Additional functions */
> +EXPORT_SYMBOL(__strnlen_user);
> +EXPORT_SYMBOL(__vmyield);
> +EXPORT_SYMBOL(__iounmap);
> +EXPORT_SYMBOL(__clear_user_hexagon);
> +EXPORT_SYMBOL(ioremap_nocache);
> +EXPORT_SYMBOL(empty_zero_page);
> +
> +/* Additional variables */
> +EXPORT_SYMBOL(_dflt_cache_att);
> +EXPORT_SYMBOL(__phys_offset);
> +EXPORT_SYMBOL(bad_dma_address);
> +
>  #define DECLARE_EXPORT(name)     \
>  	extern void name(void); EXPORT_SYMBOL(name)
>  
>  /* Symbols found in libgcc that assorted kernel modules need */
>  DECLARE_EXPORT(__hexagon_memcpy_likely_aligned_min32bytes_mult8bytes);
>  
> -DECLARE_EXPORT(__hexagon_divsi3);
> -DECLARE_EXPORT(__hexagon_modsi3);
> -DECLARE_EXPORT(__hexagon_udivsi3);
> -DECLARE_EXPORT(__hexagon_umodsi3);
> +DECLARE_EXPORT(__divsi3);
> +DECLARE_EXPORT(__modsi3);
> +DECLARE_EXPORT(__udivsi3);
> +DECLARE_EXPORT(__umodsi3);
> +
> +/* Additional functions */
> +DECLARE_EXPORT(csum_tcpudp_magic);
> 


-- 
Chen Gang

  reply	other threads:[~2013-11-29  4:03 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 [this message]
     [not found] ` <20131203011222.GA23175@codeaurora.org>
2013-12-03 12:26   ` [PATCH v3] " Chen Gang
2013-12-06 18:25     ` rkuo
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=52981222.3080007@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkuo@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).