From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kevin Diggs <kevdig@hypersurf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: function calls from identify_cpu()
Date: Sat, 03 May 2008 09:29:40 +1000 [thread overview]
Message-ID: <1209770980.26383.18.camel@pasglop> (raw)
In-Reply-To: <481B7CB4.90103@hypersurf.com>
On Fri, 2008-05-02 at 13:42 -0700, Kevin Diggs wrote:
> I added:
>
> int __init iDoNothingUseful(struct cpu_spec *s,struct cpu_spec *t)
> {
> return s-t;
> }
>
> right before the definition of identify_cpu() in cputable.c and:
>
> // (void) (*PTRRELOC(&iDoNothingUseful))(s,t);
> (void) iDoNothingUseful(s,t);
>
> right before the return s; in the match block and it will not boot? Can
> someone please explain what might be going on?
Why are you trying to muck around with that code in the first
place ? :-)
What are you trying to achieve ?
Cheers,
Ben.
next prev parent reply other threads:[~2008-05-02 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 20:42 function calls from identify_cpu() Kevin Diggs
2008-05-02 23:29 ` Benjamin Herrenschmidt [this message]
2008-05-03 5:45 ` Kevin Diggs
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=1209770980.26383.18.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=kevdig@hypersurf.com \
--cc=linuxppc-dev@ozlabs.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 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.