public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: 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: Fri, 8 Sep 2006 12:58:12 +0200	[thread overview]
Message-ID: <20060908105812.GK25473@stusta.de> (raw)
In-Reply-To: <20060908001325.GA1559@tuatara.stupidest.org>

On Thu, Sep 07, 2006 at 05:13:25PM -0700, Chris Wedgwood wrote:
> On Thu, Sep 07, 2006 at 02:03:09PM +0400, Kirill Korotaev wrote:
> 
> > At stage 2 modpost utility is used to check modules.  In case of
> > unresolved symbols modpost only prints warning.
> 
> please don't, i get bogus warnings for some drivers when
> cross-compiling, this would create problems for little or no gain

Can you give an example of such a bogus warning?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2006-09-08 10:58 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
2006-09-07 16:27         ` Andrew Morton
2006-09-08  0:13 ` Chris Wedgwood
2006-09-08 10:58   ` Adrian Bunk [this message]

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=20060908105812.GK25473@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=amirkin@sw.ru \
    --cc=cw@f00f.org \
    --cc=dev@openvz.org \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --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