From: Paul Mackerras <paulus@samba.org>
To: Matthew McClintock <msm@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC] arch/powerpc: Remove duplicate/redundant Altivec entries
Date: Wed, 8 Sep 2010 11:59:16 +1000 [thread overview]
Message-ID: <20100908015916.GB17010@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <1283885815-11175-1-git-send-email-msm@freescale.com>
On Tue, Sep 07, 2010 at 01:56:55PM -0500, Matthew McClintock wrote:
> In lieu of having multiple similiar lines, we can just have one
> generic cpu-as line for CONFIG_ALTIVEC
>
> ---
> Was hoping to get comments about this change and if anyone sees any potential
> problems?
I have a memory that we can get some altivec instructions even with
CONFIG_ALTIVEC = n, though presumably they never get executed. We
would have to check that before applying your patch.
Paul.
next prev parent reply other threads:[~2010-09-08 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 18:56 [RFC] arch/powerpc: Remove duplicate/redundant Altivec entries Matthew McClintock
2010-09-08 1:59 ` Paul Mackerras [this message]
2010-10-07 5:31 ` 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=20100908015916.GB17010@brick.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msm@freescale.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;
as well as URLs for NNTP newsgroup(s).