From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Sergey Temerkhanov <temerkhanov@cifronik.ru>,
linuxppc-dev@lists.ozlabs.org, John Linn <John.Linn@xilinx.com>
Subject: Re: [PATCHv2] [RFC] Xilinx Virtex 4 FX Soft FPU support
Date: Wed, 26 May 2010 07:50:37 -0400 [thread overview]
Message-ID: <20100526115037.GI24511@zod.rchland.ibm.com> (raw)
In-Reply-To: <AANLkTimJUqD6n9LHGZcWEkHFKvSRJsHJ9gQYMNBsIBu1@mail.gmail.com>
On Tue, May 25, 2010 at 03:38:47PM -0600, Grant Likely wrote:
>Hmmm. There should be a nicer way of doing this, but this will do for now.
>
>Otherwise, this patch looks good to me. Josh, what do you think?
I don't have any additional comments. I agree with Grant on the points he
raised, and otherwise it also looks good to me.
josh
next prev parent reply other threads:[~2010-05-26 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 10:01 [PATCHv2] [RFC] Xilinx Virtex 4 FX Soft FPU support Sergey Temerkhanov
2010-05-25 21:38 ` Grant Likely
2010-05-26 11:50 ` Josh Boyer [this message]
2010-05-26 16:32 ` Sergey Temerkhanov
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=20100526115037.GI24511@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=John.Linn@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=temerkhanov@cifronik.ru \
/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).