From: Michael Neuling <mikey@neuling.org>
To: Jimi Xenidis <jimix@pobox.com>
Cc: Andrew T Tauferner <ataufer@us.ibm.com>,
Kumar Gala <kumar.gala@gmail.com>,
Jay Bryant <jsbryant@us.ibm.com>,
Todd Inglett <tinglett@us.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC] Add IBM Blue Gene/Q Platform
Date: Mon, 10 Dec 2012 11:12:50 +1100 [thread overview]
Message-ID: <849.1355098370@neuling.org> (raw)
In-Reply-To: <17203923-C5C4-4659-9F3C-786D20C5C62E@pobox.com>
Jimi Xenidis <jimix@pobox.com> wrote:
>
> On Dec 6, 2012, at 11:41 PM, Michael Neuling <mikey@neuling.org> wrote:
>
> >> commit f6e3c1f706cb6922349d639a74ff6c50acc8b9f8
> >> Author: Jimi Xenidis <jimix@pobox.com>
> >> Date: Wed Dec 5 13:41:25 2012 -0500
> >>
> >> powerpc: Remove unecessary VSX symbols
> >>
> >> The symbol THREAD_VSR0 is defined to be the same as THREAD_FPR0. Its
> >> presence causes build issues with more complex configurations.
> >>
> >> Signed-off-by: Jimi Xenidis <jimix@pobox.com>
> >>
> >
> > Can you explain what these "complex configurations" are?
>
> In an earlier email we discussed the possibility that there was the
> possibility/desire that a single binary could support either FPU, VSX
> and the new QPX. However, if a CONFIG_VSX is not defined then
> THREAD_VSR0 does not get defined even though there might be some code
> that refers to it. Since it is an alias for the same piece of storage
> I was hoping to solve my config issue and be simplify the code.
Yep, I remember the conversation. I just want that explanation in the
commit log so others know *why* it was changed.
Mikey
next prev parent reply other threads:[~2012-12-10 0:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 1:53 [RFC] Add IBM Blue Gene/Q Platform Jimi Xenidis
2012-12-07 5:41 ` Michael Neuling
2012-12-07 13:12 ` Jimi Xenidis
2012-12-10 0:12 ` Michael Neuling [this message]
2012-12-07 5:54 ` Michael Neuling
2012-12-07 5:55 ` Michael Neuling
2012-12-07 13:38 ` Jimi Xenidis
2012-12-08 22:22 ` Jimi Xenidis
2012-12-10 0:47 ` Michael Neuling
2012-12-10 5:56 ` Jimi Xenidis
2012-12-10 6:06 ` Michael Neuling
2012-12-10 0:18 ` Michael Neuling
2012-12-07 5:56 ` Michael Neuling
2012-12-07 13:44 ` Jimi Xenidis
2012-12-07 14:31 ` Andrew Tauferner
2012-12-10 21:32 ` Jimi Xenidis
2012-12-10 21:33 ` Jimi Xenidis
2012-12-10 0:26 ` Michael Neuling
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=849.1355098370@neuling.org \
--to=mikey@neuling.org \
--cc=ataufer@us.ibm.com \
--cc=jimix@pobox.com \
--cc=jsbryant@us.ibm.com \
--cc=kumar.gala@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tinglett@us.ibm.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).