mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Steven Rostedt <srostedt@redhat.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH][for 2.6.28] Remove -mno-spe flags as they dont belong
Date: Mon, 17 Nov 2008 08:31:30 -0600	[thread overview]
Message-ID: <7D365ECF-C4B1-445C-85F9-36D4C9808E44@kernel.crashing.org> (raw)
In-Reply-To: <491F107E.4070702@redhat.com>


On Nov 15, 2008, at 12:10 PM, Steven Rostedt wrote:

> Kumar Gala wrote:
>> For some unknown reason at Steven Rostedt added in disabling of the  
>> SPE
>> instruction generation for e500 based PPC cores in commit
>> 6ec562328fda585be2d7f472cfac99d3b44d362a.
>>
>
> The unknown reason was that my PPC64 failed to compile without  
> it ;-) It was unknown because I forgot to mention that in the change  
> log (my bad).
>
> On Monday, I'll apply this patch and make sure that my PPC64 still  
> compiles.
>
> -- Steve

Thanks, if you can Ack the patch today if it works for you that would  
be great.

- k

>
>
>> We are removing it because:
>>
>> 1. It generates e500 kernels that don't work
>> 2. its not the correct set of flags to do this
>> 3. we handle this in the arch/powerpc/Makefile already
>> 4. its unknown in talking to Steven why he did this
>>
>> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
>> ---
>> kernel/Makefile |    4 +---
>> 1 files changed, 1 insertions(+), 3 deletions(-)
>


  reply	other threads:[~2008-11-17 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 18:02 Kumar Gala
2008-11-15 18:10 ` Steven Rostedt
2008-11-17 14:31   ` Kumar Gala [this message]
2008-11-17 14:33   ` Kumar Gala
2008-11-17 20:52 ` Steven Rostedt

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=7D365ECF-C4B1-445C-85F9-36D4C9808E44@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=srostedt@redhat.com \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®