From: Artem Bityutskiy <dedekind@infradead.org>
To: bene@linutronix.de
Cc: linux-mtd@lists.infradead.org,
Benedikt Spranger <b.spranger@linutronix.de>
Subject: Re: [PATCH][UBI] remove __exit on functions referenced in '.text' or '.init.text'
Date: Fri, 26 Jan 2007 15:33:41 +0200 [thread overview]
Message-ID: <1169818421.9477.30.camel@sauron> (raw)
In-Reply-To: <39678.212.184.22.162.1169809215.squirrel@www.tglx.de>
On Fri, 2007-01-26 at 12:00 +0100, bene@linutronix.de wrote:
> `ubi_sysfs_vol_close' referenced in section `.text' of drivers/built-in.o:
> defined in discarded section `.exit.text' of
> drivers/built-in.o`ubi_sysfs_vol_close' referenced in section `.text' of
> drivers/built-in.o: defined in discarded section `.exit.text' of
> drivers/built-in.o`ubi_sysfs_vol_close' referenced in section `.text' of
> drivers/built-in.o: defined in discarded section `.exit.text' of
> drivers/built-in.o`ubi_sysfs_close' referenced in section `.text' of
> drivers/built-in.o: defined in discarded section `.exit.text' of
> drivers/built-in.o`ubi_sysfs_close' referenced in section `.init.text' of
> drivers/built-in.o: defined in discarded section `.exit.text' of
> drivers/built-in.o
Hmm...
'ubi_sysfs_vol_close()' has nor __init/__exit prefix so it has to be
in .text.
But it is called from the 'delete_volumes()' function which has __exit
attribute.
So we reference 'ubi_sysfs_vol_close' which is in .text from .exit.text.
But why is this a problem?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2007-01-26 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 22:09 [PATCH][UBI] remove __exit on functions referenced in '.text' or '.init.text' Benedikt Spranger
2007-01-23 3:00 ` Josh Boyer
2007-01-24 16:30 ` Artem Bityutskiy
2007-01-26 11:00 ` bene
2007-01-26 11:39 ` Josh Boyer
2007-01-26 13:06 ` bene
2007-01-26 13:33 ` Artem Bityutskiy [this message]
2007-01-29 6:17 ` Artem Bityutskiy
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=1169818421.9477.30.camel@sauron \
--to=dedekind@infradead.org \
--cc=b.spranger@linutronix.de \
--cc=bene@linutronix.de \
--cc=linux-mtd@lists.infradead.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.