From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : arch/x86: Fix section mismatch warning for mach_x86_c1e_disable
Date: Mon, 14 Jul 2014 09:01:20 +0200 [thread overview]
Message-ID: <53C38040.4040802@siemens.com> (raw)
In-Reply-To: <53C2B020.6050209@xenomai.org>
On 2014-07-13 18:13, Gilles Chanteperdrix wrote:
> Le 10/07/2014 16:23, git repository hosting a écrit :
>> Module: xenomai-jki
>> Branch: for-forge
>> Commit: dcac4e7a3e7ccf19e4b38169e7c89eb88c821483
>> URL: http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=dcac4e7a3e7ccf19e4b38169e7c89eb88c821483
>>
>> Author: Jan Kiszka <jan.kiszka@siemens.com>
>> Date: Wed Jul 9 17:50:30 2014 +0200
>>
>> arch/x86: Fix section mismatch warning for mach_x86_c1e_disable
>>
>> mach_x86_c1e_disable is called from non-__init function mach_x86_init,
>> thus can't be tagged as __init. mach_x86_init can't be converted as it
>> is referenced by the persistent xnarch_machdesc structure.
>
> Well, it seems to me that mach_x86_init truly is an init function, is
> not there any other way to fix this?
I do not see any due the pointed out conflict around that data structure.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-07-14 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1X5FGA-00080E-2w@sd-51317.dedibox.fr>
2014-07-13 16:13 ` [Xenomai] [Xenomai-git] Jan Kiszka : arch/x86: Fix section mismatch warning for mach_x86_c1e_disable Gilles Chanteperdrix
2014-07-14 7:01 ` Jan Kiszka [this message]
2014-08-28 17:46 ` Jan Kiszka
2014-08-28 19:11 ` Gilles Chanteperdrix
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=53C38040.4040802@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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.