From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: airlied@linux.ie, torvalds@linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
Jarod Wilson <jarod@redhat.com>, Len Brown <lenb@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
drm list <dri-devel@lists.sf.net>, Ingo Molnar <mingo@elte.hu>,
Eric Anholt <eric@anholt.net>,
mjg@redhat.com, Sam Ravnborg <sam@ravnborg.org>,
x86 maintainers <x86@kernel.org>
Subject: Re: [REPOST][TRIVIAL][PATCH 1/1] Fix various section mismatches in 2.6.30-rc7
Date: Fri, 29 May 2009 13:06:25 +0530 [thread overview]
Message-ID: <1243582585.3212.6.camel@localhost.localdomain> (raw)
In-Reply-To: <430c80e90905290024n702a5210pecf9424331030a13@mail.gmail.com>
Hi Pranith,
On Fri, 2009-05-29 at 12:54 +0530, Pranith Kumar wrote:
> Hello,
>
> Fix the following section mismatches reported by
>
> $make CONFIG_DEBUG_SECTION_MISMATCH=y
>
> For the first warning, intel_lvds_init might get called after module
> has been loaded,
> intel_no_lvds shouldn't be marked __initdata.
>
> For the others the explanation is in the below warnings.
>
> WARNING: vmlinux.o(.text+0x25ad83): Section mismatch in reference from
> the function intel_lvds_init() to the variable
> .init.data:intel_no_lvds
> The function intel_lvds_init() references
> the variable __initdata intel_no_lvds.
> This is often because intel_lvds_init lacks a __initdata
> annotation or the annotation of intel_no_lvds is wrong.
>
> WARNING: vmlinux.o(.text+0x26308b): Section mismatch in reference from
> the function intel_opregion_free() to the function
> .exit.text:acpi_video_exit()
> The function intel_opregion_free() references a function in an exit section.
> Often the function acpi_video_exit() has valid usage outside the exit section
> and the fix is to remove the __exit annotation of acpi_video_exit.
>
> WARNING: vmlinux.o(__ksymtab+0x75f0): 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.
>
>
>
> Thanks,
> Pranith.
>
> Signed-off-by: D Pranith Kumar <bobby.prani@gmail.com>
> Cc: Dave Airlie <airlied@linux.ie>
>
> diff -uprN -X linux-2.6.30-rc7-vanilla/Documentation/dontdiff
> linux-2.6.30-rc7-vanilla/drivers/acpi/video.c
> linux-2.6.30-rc7/drivers/acpi/video.c
> --- linux-2.6.30-rc7-vanilla/drivers/acpi/video.c 2009-05-26
> 13:40:14.000000000 +0530
> +++ linux-2.6.30-rc7/drivers/acpi/video.c 2009-05-26 13:27:59.000000000 +0530
> @@ -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);
This patch : [PATCH 1/2 -tip] drm/i915: acpi/video.c fix
section mismatch warning" is already applied in acpi tree by Len Brown.
> diff -uprN -X linux-2.6.30-rc7-vanilla/Documentation/dontdiff
> linux-2.6.30-rc7-vanilla/drivers/gpu/drm/i915/intel_lvds.c
> linux-2.6.30-rc7/drivers/gpu/drm/i915/intel_lvds.c
> --- linux-2.6.30-rc7-vanilla/drivers/gpu/drm/i915/intel_lvds.c 2009-05-26
> 13:40:14.000000000 +0530
> +++ linux-2.6.30-rc7/drivers/gpu/drm/i915/intel_lvds.c 2009-05-26
> 13:25:50.000000000 +0530
> @@ -391,7 +391,7 @@ static int __init intel_no_lvds_dmi_call
> }
>
> /* These systems claim to have LVDS, but really don't */
> -static const struct dmi_system_id __initdata intel_no_lvds[] = {
> +static const struct dmi_system_id intel_no_lvds[] = {
> {
> .callback = intel_no_lvds_dmi_callback,
> .ident = "Apple Mac Mini (Core series)",
This patch is already in queue :
[PATCH 2/2 -tip] drm/i915: intel_lvds.c fix section mismatch warning
Thanks,
--
JSR
next prev parent reply other threads:[~2009-05-29 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <430c80e90905260118t16a51f20x48c39fd03c1331a7@mail.gmail.com>
2009-05-29 7:24 ` Pranith Kumar
2009-05-29 7:36 ` Jaswinder Singh Rajput [this message]
2009-05-29 7:40 ` Pranith Kumar
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=1243582585.3212.6.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=eric@anholt.net \
--cc=jarod@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg@redhat.com \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®