Prev: linux-next: build failure after merge of the staging-next tree
Next: [GIT PULL] kgdb fix for 2.6.34-rc5
From: Michal Simek on 30 Apr 2010 13:00
Steven J. Magnani wrote:
> Modules that use copy_{to,from}_user(), memcpy(), and memset() fail to build
> in certain circumstances.
>
> Signed-off-by: Steven J. Magnani <steve(a)digidescorp.com>
> ---
> diff -uprN a/arch/microblaze/kernel/microblaze_ksyms.c b/arch/microblaze/kernel/microblaze_ksyms.c
> --- a/arch/microblaze/kernel/microblaze_ksyms.c 2010-04-27 10:14:33.000000000 -0500
> +++ b/arch/microblaze/kernel/microblaze_ksyms.c 2010-04-27 12:52:08.000000000 -0500
> @@ -52,3 +52,13 @@ EXPORT_SYMBOL_GPL(_ebss);
> extern void _mcount(void);
> EXPORT_SYMBOL(_mcount);
> #endif
> +
> +/*
> + * Assembly functions that may be used (directly or indirectly) by modules
> + */
> +EXPORT_SYMBOL(__copy_tofrom_user);
> +
> +#ifdef CONFIG_OPT_LIB_ASM
> +EXPORT_SYMBOL(memcpy);
> +EXPORT_SYMBOL(memmove);
> +#endif
>

applied.

Thanks,
Michal


--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: linux-next: build failure after merge of the staging-next tree
Next: [GIT PULL] kgdb fix for 2.6.34-rc5