From: Vitaly Bordug <vitb@kernel•crashing.org>
To: John Tyner <jtyner@cs•ucr.edu>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] Fix 8xx compile errors
Date: Wed, 5 Dec 2007 04:09:27 +0300 [thread overview]
Message-ID: <20071205040927.4fa4e28f@kernel.crashing.org> (raw)
In-Reply-To: <20071203205837.GA22557@cs.ucr.edu>
On Mon, 3 Dec 2007 12:58:38 -0800
John Tyner wrote:
> Building for 8xx fails to compile due to errors in a couple of
> places. The first is due to the casting of an lvalue (if I remember
> correctly), and the second was due to the cpmp variable being
> declared static even though the headers previously defined it as
> extern. The following patch corrects these errors. The patch is
> against 2.4 since that's what I'm working with. (I've been unable to
> get 2.6 to run properly on my hardware so far.)
>
> Please CC me on any responses since I'm not subscribed.
>
You don't need these quirks with 2.6 and arch/powerpc... It does not use 8xx_io
and arch/powerpc/boot/* having a bit different meaning.
What is your platform btw? Adding something to 8xx camp should not be huge effort with powerpc...
--
Sincerely, Vitaly
prev parent reply other threads:[~2007-12-05 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 20:58 [PATCH] Fix 8xx compile errors John Tyner
2007-12-05 1:09 ` Vitaly Bordug [this message]
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=20071205040927.4fa4e28f@kernel.crashing.org \
--to=vitb@kernel$(echo .)crashing.org \
--cc=jtyner@cs$(echo .)ucr.edu \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/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