linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, tpowa@archlinux.org
Subject: Re: 3.13: <module> disagrees about version of symbol <symbol>
Date: Sat, 05 Apr 2014 16:29:31 +0200	[thread overview]
Message-ID: <5340134B.4010705@archlinux.org> (raw)
In-Reply-To: <20140405011332.GR32556@tassilo.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

Am 05.04.2014 03:13, schrieb Andi Kleen:
> On Tue, Apr 01, 2014 at 01:38:10AM +0200, Thomas Bächler wrote:
>> Am 01.04.2014 01:34, schrieb Andi Kleen:
>>>> This problem persists in v3.14, i.e. I still have to revert
>>>> 83460ec8dcac14142e7860a01fa59c267ac4657c in order to get a working
>>>> kernel on i686. I would really appreciate if someone would actually read
>>>> my original mail from about 3 months ago and write an answer.
>>>
>>> Can you resend it please?
>>
>> It's available here: https://lkml.org/lkml/2014/1/26/22
>>
>> For convenience, here is a copy-and-paste of the full text:
> 
> I did some experiments know and I can't find any 32bit modules 
> that do not load with 32bit MODVERSIONS on or off with 
> a current tree.
> 
> Do you have a specific config?
> Specific compiler version?

Using gcc 4.8 from Arch Linux with the configuration at [1] and Linux 3.14.

[1]
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/config?h=packages/linux


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-04-05 14:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26  9:01 3.13: <module> disagrees about version of symbol <symbol> Thomas Bächler
2014-01-26 14:22 ` Tetsuo Handa
2014-01-28  7:53   ` Thomas Bächler
2014-03-31 23:16 ` Thomas Bächler
2014-03-31 23:34   ` Andi Kleen
2014-03-31 23:38     ` Thomas Bächler
2014-04-05  1:13       ` Andi Kleen
2014-04-05 14:29         ` Thomas Bächler [this message]
2014-04-05 17:23           ` Tetsuo Handa
2014-04-05 21:47             ` Thomas Bächler
2014-04-07 17:30           ` Andi Kleen
2014-04-07 17:46             ` Thomas Bächler
2014-04-07 20:10               ` Thomas Bächler
2014-04-07 20:42                 ` Andi Kleen
2014-04-07 21:25                   ` Fleming, Matt
2014-04-07 21:30                     ` Thomas Bächler
2014-04-07 21:46                     ` Tetsuo Handa
2014-04-08 12:14                       ` Matt Fleming
2014-04-08 18:57                         ` Thomas Bächler
2014-04-08 20:04                           ` Thomas Bächler
2014-04-09  8:25                             ` Matt Fleming
2014-04-09  8:30                               ` Thomas Bächler
2014-04-09 18:01                                 ` Thomas Bächler
2014-04-09 20:43                                   ` Matt Fleming

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=5340134B.4010705@archlinux.org \
    --to=thomas@archlinux.org \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=torvalds@linux-foundation.org \
    --cc=tpowa@archlinux.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).