linux-kernel - Re: ARM: Section mismatch warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1180374973.2537.54.camel@fuzzie.sanpeople.com>
Date:	28 May 2007 19:56:14 +0200
From:	Andrew Victor <andrew@...people.com>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	ARM Linux Mailing List 
	<linux-arm-kernel@...ts.arm.linux.org.uk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: ARM: Section mismatch warnings

hi Russell,

> > o-arm-ks8695/log.out:WARNING: arch/arm/mach-ks8695/built-in.o(.data+0x108):
>  Section mismatch: reference to .init.text:micrel_pci_map_irq
>  (after 'micrel_pci')
> 
> If this platform can have PCI stuff hotplugged, then this is a problem.
> If it's fixed then it isn't - PCI IRQ routing will only be used at boot
> time.  IOW, whether such a thing is a problem is conditional on the
> hardware/configuration which I'm not aware of.

The Micrel board doesn't support hotplugged PCI devices.
I guess other KS8695-based boards can have a PCI-to-Cardbus controller,
and that would need hotpluged PCI support.

But technically that function should probably not be marked as __init.
And "struct ks8695_pci_cfg" should be __initdata.

The PCI support for the KS8695 is not currently merged in mainline.  So
I will fix this (if nobody has yet) once the PCI support goes in.


Regards,
  Andrew Victor


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/