public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Cotte-Barrot <Christian.Cotte-Barrot@bull.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Some Modules fail w/ unresolved cpu_info__per_cpu
Date: Thu, 17 Oct 2002 10:31:58 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805179@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805176@msgid-missing>

Keith Owens wrote:
> 
> On Thu, 17 Oct 2002 09:45:48 +0200,
> Christian Cotte-Barrot <Christian.Cotte-Barrot@bull.net> wrote:
> >I found that the exported symbol name via /proc/ksyms is in fact:
> >  cpu_info__per_cpu_R__ver_cpu_info__per_cpu
> >
> >Then I did not ask much more questions to me trying to find the root
> >cause of the problem within the kernel sources and I just added the
> >following trivial modification in the driver's code:
> >#define cpu_info__per_cpu   cpu_info__per_cpu_R__ver_cpu_info__per_cpu
> >
> >With this workaround insmod didn't complain anymore about "cpu_info__per_cpu"
> >and the driver works correctly.
> >
> >But I am agree it is just a workaround and we shouldn't have to
> >modify drivers's code for such problem.
> 
> Arrghh, don't do that!  FAQ: http://www.tux.org/lkml/#s8-8.

Agree, agree, agree, ...

In my case I had just the need to verify that the ipmi driver still worked
on Tiger platform and I applied a very temporary workaround in order that
the module would be successfully loaded.
I agree it is a nasty huge correction and I won't pretend it is a clean one.
I just wanted to answer I hit the problem and give an easy and simple way to
bybass it.


  parent reply	other threads:[~2002-10-17 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  1:08 [Linux-ia64] Some Modules fail w/ unresolved cpu_info__per_cpu Lee, Jung-Ik
2002-10-17  7:45 ` Christian Cotte-Barrot
2002-10-17  8:19 ` Keith Owens
2002-10-17 10:31 ` Christian Cotte-Barrot [this message]
2003-02-19 11:55 ` Christian Cotte-Barrot

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=marc-linux-ia64-105590709805179@msgid-missing \
    --to=christian.cotte-barrot@bull.net \
    --cc=linux-ia64@vger.kernel.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