From: Sam Ravnborg <sam@ravnborg.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, scsi <linux-scsi@vger.kernel.org>
Subject: Re: section mismatches (scsi e.g.)
Date: Fri, 14 Apr 2006 18:53:36 +0200 [thread overview]
Message-ID: <20060414165336.GB4053@mars.ravnborg.org> (raw)
In-Reply-To: <1145033415.3520.36.camel@mulgrave.il.steeleye.com>
On Fri, Apr 14, 2006 at 11:50:15AM -0500, James Bottomley wrote:
> On Fri, 2006-04-14 at 09:29 -0700, Randy.Dunlap wrote:
> > WARNING: drivers/scsi/3w-9xxx.o - Section mismatch: reference to .init.data: from .data between 'twa_driver' (at offset 0x18) and 'twa_error_table'
> > WARNING: drivers/scsi/3w-xxxx.o - Section mismatch: reference to .init.data: from .data between 'tw_driver' (at offset 0x18) and 'tw_sense_table'
> > WARNING: drivers/scsi/gdth.o - Section mismatch: reference to .init.text:gdth_detect from .data between 'driver_template' (at offset 0x270) and 'async_cache_tab'
> >
> > I either don't see a problem or I'm having trouble reading/decoding
> > the warning messages. Could you look at these 3 sometime?
>
> These seem to have been turning up all over the tree. The only common
> feature seems to be that if you re-run the build, they don't show up
> again.
I really hope this is not true. The reporting ought to be conistent.
If you can give me something reproduceable then I will try to hunt it
down.
Sam
next prev parent reply other threads:[~2006-04-14 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 16:29 section mismatches (scsi e.g.) Randy.Dunlap
2006-04-14 16:50 ` James Bottomley
2006-04-14 16:53 ` Sam Ravnborg [this message]
2006-04-14 16:52 ` Sam Ravnborg
2006-04-14 18:27 ` Randy.Dunlap
2006-04-14 19:25 ` Randy.Dunlap
2006-04-14 21:21 ` Sam Ravnborg
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=20060414165336.GB4053@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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