Re: [PATCH] x86: fix section mismatch warnings in mtrr

> The whole purpose with __init and friends are the possibility to drop
> the .init.text (+ .init.data) section when the kernel is up and running.

I know what they do, you don't need to repeatedly reexplain them.

My point was just that in all the __init/__initdata warnings I recently fixed
personally there wasn't a single one that wasn't a false positive and frankly I don't
see any sign of them really showing real bugs. Basically effort:gain doesn't
seem to be well balanced here.

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

---

• References:
  • 2.6.22-rc2: section mismatch
    • From: Andrey Borzenkov <[email protected]>
  • Re: [PATCH] x86: fix section mismatch warnings in mtrr
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH] x86: fix section mismatch warnings in mtrr
    • From: Sam Ravnborg <[email protected]>

• Prev by Date: [PATCH] mtd/ubi: silence gcc warning
• Next by Date: Re: 2.6.21.1 - 97% wait time on IDE operations
• Previous by thread: Re: [PATCH] x86: fix section mismatch warnings in mtrr
• Next by thread: 2.6.22-rc2: regression: STD fails with pci_device_suspend(): usb_hcd_pci_suspend+0x0/0x160 [usbcore]() returns -16
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]