linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: linuxppc-dev@ozlabs.org, Nate Case <ncase@xes-inc.com>,
	ths@linutronix.de
Subject: Re: [PATCH] powerpc: enforce a non-spe kernel build even on broken compilers
Date: Wed, 15 Oct 2008 08:25:54 -0500	[thread overview]
Message-ID: <6115D7FB-7500-4F67-B02B-B64B92B33D1A@kernel.crashing.org> (raw)
In-Reply-To: <20081015085904.GA28369@Chamillionaire.breakpoint.cc>


On Oct 15, 2008, at 3:59 AM, Sebastian Andrzej Siewior wrote:

> * Sebastian Andrzej Siewior | 2008-10-15 00:49:46 [+0200]:
>
>>> is the -mabi=no-spe really needed?
>> It seems to work the other way around (without -mabi=no-spe but with
>> -mabi=no-spe) alteast I did not find anything in do_syslog() or while
>> browsing through the dissasm. I do a boot check tomorrow.
>
> Okay. I recompiled with -mspe=no and was able to boot without trouble.
> It didn't work with -mabi=no-spe.

I'm confused.. what did you change from your patch?

- k

  reply	other threads:[~2008-10-15 13:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 14:23 [PATCH] powerpc: enforce a non-spe kernel build even on broken compilers Sebastian Siewior
2008-10-14 19:25 ` Nate Case
2008-10-14 22:02   ` Nate Case
2008-10-14 21:23 ` Kumar Gala
2008-10-14 22:35   ` Nate Case
2008-10-14 22:49   ` Sebastian Andrzej Siewior
2008-10-15  8:59     ` Sebastian Andrzej Siewior
2008-10-15 13:25       ` Kumar Gala [this message]
2008-10-15 14:43         ` Sebastian Andrzej Siewior
2008-10-15 16:31           ` Kumar Gala
2008-10-17 14:02           ` Nate Case
2008-10-17 15:01             ` Sebastian Andrzej Siewior
2008-10-24 23:51             ` Nate Case
2008-10-24 23:55               ` Kumar Gala

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=6115D7FB-7500-4F67-B02B-B64B92B33D1A@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ncase@xes-inc.com \
    --cc=sebastian@breakpoint.cc \
    --cc=ths@linutronix.de \
    /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).