From: Nico -telmich- Schottelius <nico-linux-next@schottelius•org>
To: Gabriel C <nix.or.die@googlemail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: Invalid module format (was: Re: linux-next: Tree for April 1)
Date: Wed, 1 Apr 2009 18:03:33 +0200 [thread overview]
Message-ID: <20090401160333.GA5249@denkbrett.schottelius.org> (raw)
In-Reply-To: <1820d69d0904010852qc07ccc7qc9cec18bcc2837bd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Gabriel C [Wed, Apr 01, 2009 at 05:52:59PM +0200]:
> 2009/4/1 Nico -telmich- Schottelius <nico-linux-next@schottelius•org>:
> > Stephen Rothwell [Wed, Apr 01, 2009 at 04:44:50PM +1100]:
> >> Hi all,
> >>
> >> Changes since 20090331:
> >
> > Same problem since 20090324.
>
> AFAIK it is since 20090218...
>
> >
> > arch=amd64, config attached, all modules have that problem.
>
> Disabling CONFIG_MODVERSIONS should workaround this problem.
Ahh, thanks! So I'll trac wireless-testing and iwlwifi for now, they
do have enough bugs for me :-)
Sincerly,
Nico
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-01 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 5:44 linux-next: Tree for April 1 Stephen Rothwell
2009-04-01 10:27 ` [Patch next] powerpc: pseries/dtl.c should include asm/firmware.h Sachin Sant
2009-04-02 0:34 ` Michael Neuling
2009-04-02 5:31 ` Sachin Sant
2009-04-01 15:09 ` Invalid module format (was: Re: linux-next: Tree for April 1) Nico -telmich- Schottelius
2009-04-01 15:52 ` Gabriel C
2009-04-01 16:03 ` Nico -telmich- Schottelius [this message]
2009-04-02 1:32 ` Stephen Rothwell
2009-04-06 11:22 ` Invalid module format Gabriel C
2009-04-07 3:14 ` James Morris
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=20090401160333.GA5249@denkbrett.schottelius.org \
--to=nico-linux-next@schottelius$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nix.or.die@googlemail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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