All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Nico -telmich- Schottelius <nico-linux-next@schottelius.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Invalid module format
Date: Mon, 06 Apr 2009 13:22:13 +0200	[thread overview]
Message-ID: <49D9E5E5.9080505@googlemail.com> (raw)
In-Reply-To: <20090402123223.f31370cd.sfr@canb.auug.org.au>

Stephen Rothwell wrote:

> Hi Nico,
> 
> On Wed, 1 Apr 2009 17:09:28 +0200 Nico -telmich- Schottelius <nico-linux-next@schottelius.org> wrote:
>> Stephen Rothwell [Wed, Apr 01, 2009 at 04:44:50PM +1100]:
>>> Changes since 20090331:
>> Same problem since 20090324.
>>
>> arch=amd64, config attached, all modules have that problem.
> 
> Does Linus' kernel with this config show the problem?
> 


Now it does , CONFIG_MODVERSIONS is broken in Linus tree too.

I reverted this commit :

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9cb610d8e35fe3ec95a2fe2030b02f85aeea83c1

and after that modules loading seems to work again here.


Gabriel

 

  reply	other threads:[~2009-04-06 11:21 UTC|newest]

Thread overview: 32+ 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-01 10:27   ` Sachin Sant
2009-04-02  0:34   ` Michael Neuling
2009-04-02  0:34     ` Michael Neuling
2009-04-02  5:31     ` Sachin Sant
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
2009-04-02  1:32   ` Stephen Rothwell
2009-04-06 11:22     ` Gabriel C [this message]
2009-04-07  3:14       ` Invalid module format James Morris
  -- strict thread matches above, loose matches on Subject: below --
2009-09-09 16:14 Edouard Marquez
2009-09-09 16:19 ` Devin Heitmueller
     [not found]   ` <c2885d2b0909091113h2ae6e27ai7541b3efac0e4606@mail.gmail.com>
2009-09-09 18:20     ` Devin Heitmueller
     [not found]       ` <c2885d2b0909091134w1264b827kf5d4254634bed1d9@mail.gmail.com>
2009-09-09 18:39         ` Devin Heitmueller
2009-09-09 19:02   ` Markus Rechberger
2009-09-09 19:08     ` Markus Rechberger
2009-09-09 19:09     ` Devin Heitmueller
2009-09-09 19:40       ` Markus Rechberger
2018-02-21 21:12 Srishti Sharma
2018-02-21 21:24 ` valdis.kletnieks at vt.edu
     [not found] ` <BY1PR0101MB101393E19DAD4C4C584BD89BCDCE0@BY1PR0101MB1013.prod.exchangelabs.com>
     [not found]   ` <CAB3L5ozA_VUAJiypue2RDN-_kuC7FnS+DaYPO7cOfTKb9dBLAw@mail.gmail.com>
2018-02-21 21:39     ` Alejandro D?az
2018-02-23 23:29 ` Tobin C. Harding
2018-02-24  3:06   ` valdis.kletnieks at vt.edu
2018-02-25  2:34     ` Tobin C. Harding
2018-02-25  5:04       ` valdis.kletnieks at vt.edu
2018-02-25  7:29         ` Tobin C. Harding
2018-02-24  5:06   ` Srishti Sharma
2018-02-24  5:15 Alex Arvelaez
2018-02-24  5:17 ` Srishti Sharma

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=49D9E5E5.9080505@googlemail.com \
    --to=nix.or.die@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nico-linux-next@schottelius.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.