All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Fix section conflict of ia64_mlogbuf_finish
Date: Wed, 16 May 2007 00:43:18 +0000	[thread overview]
Message-ID: <464A53A6.2050509@jp.fujitsu.com> (raw)
In-Reply-To: <20070515164202.GA19839@deprecation.cyrius.com>

 >> I suspect EXPORT is left over from the initial development/debug.

Yes, that's right.

The reason why the EXPORT was there is that I supposed a optional use
of ia64_mlogbuf_finish expecting that there would be some non-standard
mca recovery module, module relating kdump or something.
However such module is not there at the moment.

Thanks,
H.Seto

Martin Michlmayr wrote:
> * Russ Anderson <rja@sgi.com> [2007-05-15 13:32]:
>> I suspect EXPORT is left over from the initial development/debug.
>> Either change is fine with me.
> 
> OK, then let's use this one instead:
> 
> 
> Subject: Fix section conflict of ia64_mlogbuf_finish
> 
> Building with GCC 4.2, I get the following error:
> 
>   CC      arch/ia64/kernel/mca.o
> arch/ia64/kernel/mca.c:275: error: __ksymtab_ia64_mlogbuf_finish causes a
> section type conflict
> 
> This is because ia64_mlogbuf_finish is both declared static and exported.
> 
> Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
> 
> --- a/arch/ia64/kernel/mca.c
> +++ b/arch/ia64/kernel/mca.c
> @@ -272,7 +272,6 @@ static void ia64_mlogbuf_finish(int wait)
>  
>  	mlogbuf_finished = 1;
>  }
> -EXPORT_SYMBOL(ia64_mlogbuf_finish);
>  
>  /*
>   * Print buffered messages from INIT context.
> 

      parent reply	other threads:[~2007-05-16  0:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 16:42 Fix section conflict of ia64_mlogbuf_finish Martin Michlmayr
2007-05-15 16:50 ` Luck, Tony
2007-05-15 18:32 ` Russ Anderson
2007-05-15 19:03 ` Martin Michlmayr
2007-05-16  0:43 ` Hidetoshi Seto [this message]

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=464A53A6.2050509@jp.fujitsu.com \
    --to=seto.hidetoshi@jp.fujitsu.com \
    --cc=linux-ia64@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.