netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
	Val Henson <val_henson@linux.intel.com>,
	netdev@vger.kernel.org, Helge Deller <deller@parisc-linux.org>,
	Kyle McMartin <kyle@parisc-linux.org>
Subject: Re: [PATCH] [TULIP] Fix section mismatch in de2104x.c
Date: Fri, 06 Oct 2006 15:18:33 -0400	[thread overview]
Message-ID: <4526AC09.4040804@garzik.org> (raw)
In-Reply-To: <20061006110317.0c6c1f98@freekitty>

Stephen Hemminger wrote:
> On Fri, 06 Oct 2006 12:12:34 -0600
> Matthew Wilcox <matthew@wil.cx> wrote:
> 
>> From: Helge Deller <deller@parisc-linux.org>
>>
>> WARNING: drivers/net/tulip/de2104x.o - Section mismatch: reference to .init.text:de_init_one from .data.rel.local after 'de_driver' (at offset 0x20)
>> WARNING: drivers/net/tulip/de2104x.o - Section mismatch: reference to .exit.text:de_remove_one from .data.rel.local after 'de_driver' (at offset 0x28)
> 
> This is caused because with PCI hotplug the device might be probed after the init section
> has been removed.  Ditto for remove.

This device will never ever meet a platform where it can be hotplugged.

	Jeff




  reply	other threads:[~2006-10-06 19:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 18:12 [PATCH] [TULIP] Fix section mismatch in de2104x.c Matthew Wilcox
2006-10-06 18:03 ` Stephen Hemminger
2006-10-06 19:18   ` Jeff Garzik [this message]
2006-10-06 19:25     ` Matthew Wilcox
2006-10-06 19:44       ` Jeff Garzik
2006-10-06 19:54         ` Matthew Wilcox
2006-10-06 20:11           ` Jeff Garzik
2006-10-06 18:39 ` Jeff Garzik
2006-10-06 18:45   ` Matthew Wilcox
2006-10-06 18:50     ` Jeff Garzik
2006-10-06 19:25   ` More info on section mismatches (was Re: [PATCH] [TULIP] Fix section mismatch in de2104x.c) Valerie Henson

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=4526AC09.4040804@garzik.org \
    --to=jeff@garzik.org \
    --cc=deller@parisc-linux.org \
    --cc=kyle@parisc-linux.org \
    --cc=matthew@wil.cx \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=val_henson@linux.intel.com \
    /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).