From: Prarit Bhargava <prarit@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH]: -mm tree remove __exit from loop_exit
Date: Thu, 31 May 2007 15:58:14 +0000 [thread overview]
Message-ID: <20070531155814.21159.454.sendpatchset@prarit.boston.redhat.com> (raw)
I sent this to lkml (and a large # of cc's). Tony, please do not pick this
up in your tree. I'm posting this here just so SGI users have this info ...
P.
Andrew, please patch ASAP as compile on SGI ia64 is broken. Please note this
patch does not address why modpost did not pick up this error.
ie) ./scripts/mod/modpost drivers/block/built-in.o yields no information about
the section mismatch. AFAIK, it should spit out a loud WARNING.
Patch against 2.6.22-rc3-mm1.
Current mm tree does not build with sn2_defconfig. Build results in error:
`.exit.text' referenced in section `.init.text' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o
make: *** [.tmp_vmlinux1] Error 1
__exit loop_exit is now being called from __init loop_init which causes this error.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
--- linux/drivers/block/loop.c.orig 2007-05-31 11:15:21.000000000 -0400
+++ linux/drivers/block/loop.c 2007-05-31 11:11:05.000000000 -0400
@@ -1456,7 +1456,7 @@ static struct kobject *loop_probe(dev_t
return kobj;
}
-static void __exit loop_exit(void)
+static void loop_exit(void)
{
unsigned long range;
struct loop_device *lo, *next;
next reply other threads:[~2007-05-31 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 15:58 Prarit Bhargava [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-31 15:56 [PATCH]: -mm tree remove __exit from loop_exit Prarit Bhargava
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=20070531155814.21159.454.sendpatchset@prarit.boston.redhat.com \
--to=prarit@redhat.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.