public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <dev@sw.ru>
To: Olaf Hering <olaf@aepfle.de>
Cc: Adrian Bunk <bunk@stusta.de>, Kirill Korotaev <dev@openvz.org>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrey Mirkin <amirkin@sw.ru>,
	devel@openvz.org, mikpe@it.uu.se, sam@ravnborg.org
Subject: Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
Date: Thu, 07 Sep 2006 19:23:49 +0400	[thread overview]
Message-ID: <45003985.7060304@sw.ru> (raw)
In-Reply-To: <20060907122607.GA22882@aepfle.de>

Olaf Hering wrote:
> 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.
It is not that sudden at all. I experienced this problem many times so far
and working with a build system came to the idea of failing
builds when there are unresolved symbols.

I'm pretty sure that having this patch in mainstream
will make unresolved symbols a rare problem as many of them will be fixed soon.
So I'm pretty agree with Adrian that modules with unresolved symbols is a bug
and it MUST be fixed.
I would be very much interested to hear Andrew opinion on this as
he probably makes kernels even more often than any of us :)

Thanks,
Kirill


  reply	other threads:[~2006-09-07 15:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 10:03 [PATCH] fail kernel compilation in case of unresolved symbols (v2) Kirill Korotaev
2006-09-07 11:05 ` Olaf Hering
2006-09-07 11:13   ` Adrian Bunk
2006-09-07 12:26     ` Olaf Hering
2006-09-07 15:23       ` Kirill Korotaev [this message]
2006-09-07 16:27         ` Andrew Morton
2006-09-08  0:13 ` Chris Wedgwood
2006-09-08 10:58   ` Adrian Bunk

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=45003985.7060304@sw.ru \
    --to=dev@sw.ru \
    --cc=akpm@osdl.org \
    --cc=amirkin@sw.ru \
    --cc=bunk@stusta.de \
    --cc=dev@openvz.org \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=olaf@aepfle.de \
    --cc=sam@ravnborg.org \
    /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