Re: [PATCH] fallout from kbuild changes

BTW, the presense of vmlinux in the second modpost generates warnings
in two cases - i386 with CONFIG_RELOCATABLE and sparc32 (always).
The warnings tend to be bogus.  Do we really want them there now that
we should (in theory) get all useful stuff from vmlinux.o?  Other
targets get aways with that since they don't have relocs survive into
vmlinux...
-
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/

---

• Follow-Ups:
  • Re: [PATCH] fallout from kbuild changes
    • From: Sam Ravnborg <[email protected]>

• References:
  • [PATCH] fallout from kbuild changes
    • From: Al Viro <[email protected]>
  • Re: [PATCH] fallout from kbuild changes
    • From: Sam Ravnborg <[email protected]>

• Prev by Date: [GIT PULL] Trivial sh64 updates for 2.6.23-rc1
• Next by Date: Re: kobject link failure
• Previous by thread: Re: [PATCH] fallout from kbuild changes
• Next by thread: Re: [PATCH] fallout from kbuild changes
• 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]