public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Arkadiusz Miskiewicz <arekm@pld-linux.org>,
	Andrew Morton <akpm@osdl.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: modules in 2.6 kernel - question for FAQ?
Date: Thu, 15 Apr 2004 14:54:20 +1000	[thread overview]
Message-ID: <1082004860.17780.143.camel@bach> (raw)
In-Reply-To: <20040415044452.GA2215@mars.ravnborg.org>

On Thu, 2004-04-15 at 14:44, Sam Ravnborg wrote:
> On Thu, Apr 15, 2004 at 11:52:48AM +1000, Rusty Russell wrote:
> > On Thu, 2004-04-15 at 05:42, Arkadiusz Miskiewicz wrote:
> > > insmod: error inserting './Intel537.ko': -1 Invalid module format
> > 
> > They didn't use -fno-common.  The patch which adds in the warning got
> > lost a while back.
> > 
> > Here's a new one...
> 
> Is it be possible to detect this during the modpost stage, or do they manage to
> avoid that in some way?
> I would rather see the error a bit earlier. Eventually depmod.
> Still your patch make relevance as a double check.

They can only do this if they're not using the kernel makefiles.  So I
don't really think it's a priority...

Cheers,
Rusty.
-- 
Anyone who quotes me in their signature is an idiot -- Rusty Russell


  reply	other threads:[~2004-04-15  4:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200404142142.41137.arekm@pld-linux.org>
2004-04-15  1:52 ` modules in 2.6 kernel - question for FAQ? Rusty Russell
2004-04-15  4:44   ` Sam Ravnborg
2004-04-15  4:54     ` Rusty Russell [this message]
2004-04-15 13:41       ` Chris Friesen
2004-04-15 13:56         ` Arjan van de Ven
2004-04-15 14:57           ` Chris Friesen

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=1082004860.17780.143.camel@bach \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@osdl.org \
    --cc=arekm@pld-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --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