linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Jarod Wilson <jarod@redhat.com>, Len Brown <lenb@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Dave Airlie <airlied@linux.ie>, drm list <dri-devel@lists.sf.net>
Cc: 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: Re: [PATCH 2/2 -tip] drm/i915: intel_lvds.c fix section mismatch warning
Date: Fri, 29 May 2009 11:46:35 +0530	[thread overview]
Message-ID: <1243577795.3159.27.camel@localhost.localdomain> (raw)
In-Reply-To: <200905281100.21386.jarod@redhat.com>

On Thu, 2009-05-28 at 11:00 -0400, Jarod Wilson wrote:
> On Wednesday 20 May 2009 02:27:35 Jaswinder Singh Rajput wrote:
> > 
> > intel_no_lvds[] does not require __initdata as it is used only by :
> > 
> >   void intel_lvds_init(struct drm_device *dev)
> > 
> > fixes section mismatch warning:
> > 
> >   WARNING: drivers/gpu/drm/i915/i915.o(.text+0xf3c5): 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
> 
> This would seem to suggest __initdata should be added to
> intel_lvds_init, rather than removed from intel_no_lvds...
> 

The complete statement is :

WARNING: drivers/gpu/drm/i915/i915.o(.text+0xf3c5): 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.

> But I suppose either one would work. Apologies for not
> catching the initial mismatch... :\
> 

No another way it will not work.

As intel_no_lvds is used by intel_lvds_init and dmi_check_system.

We can not set intel_lvds_init as intel_lvds_init is used by :
  static void intel_setup_outputs(struct drm_device *dev)

We can not set dmi_check_system to __init as it is also exported.

So the only option is to remove __initdata.

It seems the first patch : "[PATCH 1/2 -tip] drm/i915: acpi/video.c fix
section mismatch warning" is applied in acpi tree by Len Brown.

I am not sure where this patch should go.

So I am also mailing to Andrew and Dave, it they find this useful then
they can add in their tree.

> > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> > ---
> >  drivers/gpu/drm/i915/intel_lvds.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_lvds.c b/drivers/gpu/drm/i915/intel_lvds.c
> > index 439a865..5ffadf9 100644
> > --- a/drivers/gpu/drm/i915/intel_lvds.c
> > +++ b/drivers/gpu/drm/i915/intel_lvds.c
> > @@ -391,7 +391,7 @@ static int __init intel_no_lvds_dmi_callback(const struct dmi_system_id *id)
> >  }
> >  
> >  /* 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)",
> 
> 


  reply	other threads:[~2009-05-29  6:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  6:26 [PATCH 1/2 -tip] drm/i915: acpi/video.c fix section mismatch warning Jaswinder Singh Rajput
2009-05-20  6:27 ` [PATCH 2/2 -tip] drm/i915: intel_lvds.c " Jaswinder Singh Rajput
2009-05-28 15:00   ` Jarod Wilson
2009-05-29  6:16     ` Jaswinder Singh Rajput [this message]
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=1243577795.3159.27.camel@localhost.localdomain \
    --to=jaswinder@kernel.org \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --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=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).