From: Jon Loeliger <jdl@freescale.com>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: Compilation error in fsl_soc.c
Date: Mon, 31 Jul 2006 15:45:15 -0500 [thread overview]
Message-ID: <1154378714.5107.44.camel@cashmere.sps.mot.com> (raw)
In-Reply-To: <20060731173959.03f57dd4@vitb.ru.mvista.com>
On Mon, 2006-07-31 at 08:39, Vitaly Bordug wrote:
> On Mon, 31 Jul 2006 08:37:56 +0100
> "Demke Torsten-atd012" <torsten.demke@motorola.com> wrote:
>
> > Hi all,
> >
> > with a recent versions from Paulus merge-tree the compilation
> > of MPC85xx CDS failed with following output:
> > ...
>
> No, since it is just going to be out.
>
> I'll submit some patches addressing that this week...
Vitaly,
I have just posted some patches on linuxppc-dev
for the 86xx that cover the fsl_soc.c breakage here.
Thanks,
jdl
prev parent reply other threads:[~2006-07-31 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 7:37 Compilation error in fsl_soc.c Demke Torsten-atd012
2006-07-31 13:39 ` Vitaly Bordug
2006-07-31 20:45 ` Jon Loeliger [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=1154378714.5107.44.camel@cashmere.sps.mot.com \
--to=jdl@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@ru.mvista.com \
/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