public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Various section mismatches
Date: Thu, 06 Mar 2008 04:37:57 +0000	[thread overview]
Message-ID: <20080306043757.GA18164@linux-sh.org> (raw)
In-Reply-To: <1202080862.9936.4.camel@localhost.localdomain>

On Sun, Feb 03, 2008 at 11:21:02PM +0000, Adrian McMenamin wrote:
>   LD      drivers/video/built-in.o
> WARNING: drivers/video/built-in.o(.text+0xd980): Section mismatch in reference from the function pvr2fb_check_var() to the variable .devinit.data:pvr2fb_pci_tbl
> The function  pvr2fb_check_var() references
> the variable __devinitdata pvr2fb_pci_tbl.
> This is often because pvr2fb_check_var lacks a __devinitdata 
> annotation or the annotation of pvr2fb_pci_tbl is wrong.
> 
These should all basically be fixed by now. This was the only outstanding
one, and was a bit of a pain to track down since DEBUG_SECTION_MISMATCH
didn't seem to have any clue what it was talking about. A few updates
later it managed to get a bit closer to the actual offending symbol
(presently it's convinced that pvr2_fix is the proble, which is at least
quite a bit closer to reality), but was still wrong. The problem ended up
being the pvr2_var.vmode reference in pvr2fb_check_var(), which I just
replaced with an explicit reference to FB_VMODE_NONINTERLACED. I'll push
that out for 2.6.25, and hopefully that should be the last of them.

      parent reply	other threads:[~2008-03-06  4:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 23:21 Various section mismatches Adrian McMenamin
2008-02-04  1:12 ` Paul Mundt
2008-02-04  8:25 ` Adrian McMenamin
2008-03-06  4:37 ` Paul Mundt [this message]

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=20080306043757.GA18164@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox