From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Ingo Molnar <mingo@elte.hu>, Eric Anholt <eric@anholt.net>,
mjg@redhat.com, Sam Ravnborg <sam@ravnborg.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2 -tip] drm/i915: acpi/video.c fix section mismatch warning
Date: Wed, 20 May 2009 11:56:08 +0530 [thread overview]
Message-ID: <1242800768.3260.21.camel@localhost.localdomain> (raw)
Currently acpi_video_exit() is exported as well as using __exit which causes:
WARNING: drivers/acpi/video.o(__ksymtab+0x0): Section mismatch in reference from the variable __ksymtab_acpi_video_exit to the function .exit.text:acpi_video_exit()
The symbol acpi_video_exit is exported and annotated __exit
Fix this by removing the __exit annotation of acpi_video_exit or drop the export.
Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
---
drivers/acpi/video.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
index 810cca9..a79b885 100644
--- a/drivers/acpi/video.c
+++ b/drivers/acpi/video.c
@@ -2334,7 +2334,7 @@ static int __init acpi_video_init(void)
return acpi_video_register();
}
-void __exit acpi_video_exit(void)
+void acpi_video_exit(void)
{
acpi_bus_unregister_driver(&acpi_video_bus);
--
1.6.1.1
next reply other threads:[~2009-05-20 6:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 6:26 Jaswinder Singh Rajput [this message]
2009-05-20 6:27 ` [PATCH 2/2 -tip] drm/i915: intel_lvds.c fix section mismatch warning Jaswinder Singh Rajput
2009-05-28 15:00 ` Jarod Wilson
2009-05-29 6:16 ` Jaswinder Singh Rajput
2009-05-29 13:34 ` Jarod Wilson
2009-05-29 14:28 ` Jaswinder Singh Rajput
2009-06-01 10:53 ` Jesse Barnes
2009-06-01 11:25 ` Jaswinder Singh Rajput
2009-05-26 20:00 ` [PATCH 1/2 -tip] drm/i915: acpi/video.c " Len Brown
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=1242800768.3260.21.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg@redhat.com \
--cc=sam@ravnborg.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).