Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)

On Thu, Sep 07, Adrian Bunk wrote:

> If any module shipped with the kernel has in any configuration 
> unresolved symbols that's a bug that should be reported, not ignored.

Yes, but on request when building the package. Not per default.
I probably missed the reason why this is now suddenly a problem.
-
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] fail kernel compilation in case of unresolved symbols (v2)
  - From: Kirill Korotaev <[email protected]>

References:
- [PATCH] fail kernel compilation in case of unresolved symbols (v2)
  - From: Kirill Korotaev <[email protected]>
- Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
  - From: Olaf Hering <[email protected]>
- Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
  - From: Adrian Bunk <[email protected]>

Prev by Date: Re: question regarding cacheline size
Next by Date: Re: question regarding cacheline size
Previous by thread: Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
Next by thread: Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
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]