All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: Add EXPORT_SYMBOL(min_low_pfn) and EXPORT_SYMBOL(max_low_pfn) to sh_ksyms_32.c
Date: Fri, 13 Dec 2013 02:42:10 +0000	[thread overview]
Message-ID: <52AA7402.1050806@renesas.com> (raw)
In-Reply-To: <1386893438-23573-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com>

Hi,

(2013/12/13 10:12), Kuninori Morimoto wrote:
> 
> Hi
> 
>> Min_low_pfn and max_low_pfn were used in pfn_valid macro if defined
>> CONFIG_FLATMEM. When the functions that use the pfn_valid is used in driver
>> module, max_low_pfn and min_low_pfn is to undefined, and fail to build.
>>
>> ----
>> ERROR: "min_low_pfn" [drivers/block/aoe/aoe.ko] undefined!
>> ERROR: "max_low_pfn" [drivers/block/aoe/aoe.ko] undefined!
>> make[2]: *** [__modpost] Error 1
>> make[1]: *** [modules] Error 2
>> ----
> (snip)
>> +#ifdef CONFIG_FLATMEM
>> +/* need in pfn_valid macro */
>> +EXPORT_SYMBOL(min_low_pfn);
>> +EXPORT_SYMBOL(max_low_pfn);
>> +#endif
> 
> I'm not sure detail of min/max_low_pfn,
> but these exist under ${LINUX}/mm/[no]bootmem.c ?
> 

Yes, I know.

> EXPORT_SYMBOL() on arch/sh/kernel/sh_ksyms_32.c
> seems strange for me.

Handling of these depends on CPUs.
And in SH32, it may be referred to from modules.
Therefore, I have feeling that it is not amusing that sh_ksyms_32.c defines these using EXPORT_SYMBOL.

Would you explain the reason that you thought to be strange?

> 
> Best regards
> ---
> Kuninori Morimoto

Best regards,
  Nobuhiro



  parent reply	other threads:[~2013-12-13  2:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13  0:10 [PATCH] sh: Add EXPORT_SYMBOL(min_low_pfn) and EXPORT_SYMBOL(max_low_pfn) to sh_ksyms_32.c Nobuhiro Iwamatsu
2013-12-13  1:12 ` Kuninori Morimoto
2013-12-13  2:42 ` Nobuhiro Iwamatsu [this message]
2013-12-13  3:17 ` Kuninori Morimoto
2013-12-13  6:25 ` Nobuhiro Iwamatsu
2013-12-13  7:56 ` Andrew Morton
2013-12-13  8:51 ` Geert Uytterhoeven
2013-12-13 20:59 ` Andrew Morton
2013-12-16  1:13 ` Nobuhiro Iwamatsu
2013-12-16  1:28 ` Nobuhiro Iwamatsu
2013-12-16 13:25 ` Geert Uytterhoeven
2013-12-18  0:12 ` Nobuhiro Iwamatsu

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=52AA7402.1050806@renesas.com \
    --to=nobuhiro.iwamatsu.yj@renesas.com \
    --cc=linux-sh@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.