From: Christoph Hellwig <hch@infradead.org>
To: Alan Kao <alankao@andestech.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@sifive.com>, Albert Ou <albert@sifive.com>,
Christoph Hellwig <hch@infradead.org>,
Andrew Waterman <andrew@sifive.com>,
Arnd Bergmann <arnd@arndb.de>, Darius Rad <darius@bluespec.com>,
Vincent Chen <vincentc@andestech.com>,
Zong Li <zong@andestech.com>, Nick Hu <nickhu@andestech.com>,
Greentime Hu <greentime@andestech.com>
Subject: Re: [PATCH v4 4/5] Allow to disable FPU support
Date: Wed, 8 Aug 2018 00:07:58 -0700 [thread overview]
Message-ID: <20180808070758.GA27402@infradead.org> (raw)
In-Reply-To: <1533698685-18022-5-git-send-email-alankao@andestech.com>
On Wed, Aug 08, 2018 at 11:24:44AM +0800, Alan Kao wrote:
> FPU codes have been separated from common part in previous patches.
> This patch add the CONFIG_FPU option and some stubs, so that a no-FPU
> configuration is allowed.
>
> Signed-off-by: Alan Kao <alankao@andestech.com>
> Cc: Greentime Hu <greentime@andestech.com>
> Cc: Vincent Chen <vincentc@andestech.com>
> Cc: Zong Li <zong@andestech.com>
> Cc: Nick Hu <nickhu@andestech.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2018-08-08 7:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 3:24 [PATCH v4 0/5] riscv: Add support to no-FPU systems Alan Kao
2018-08-08 3:24 ` [PATCH v4 1/5] Extract FPU context operations from entry.S Alan Kao
2018-08-08 3:24 ` [PATCH v4 2/5] Refactor FPU code in signal setup/return procedures Alan Kao
2018-08-08 3:24 ` [PATCH v4 3/5] Cleanup ISA string setting Alan Kao
2018-08-20 22:22 ` Palmer Dabbelt
2018-08-21 2:47 ` Alan Kao
2018-08-21 19:36 ` Palmer Dabbelt
2018-08-08 3:24 ` [PATCH v4 4/5] Allow to disable FPU support Alan Kao
2018-08-08 7:07 ` Christoph Hellwig [this message]
2018-08-08 3:24 ` [PATCH v4 5/5] Auto-detect whether a FPU exists Alan Kao
2018-08-08 7:18 ` Christoph Hellwig
2018-08-20 22:22 ` [PATCH v4 0/5] riscv: Add support to no-FPU systems Palmer Dabbelt
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=20180808070758.GA27402@infradead.org \
--to=hch@infradead.org \
--cc=alankao@andestech.com \
--cc=albert@sifive.com \
--cc=andrew@sifive.com \
--cc=arnd@arndb.de \
--cc=darius@bluespec.com \
--cc=greentime@andestech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nickhu@andestech.com \
--cc=palmer@sifive.com \
--cc=vincentc@andestech.com \
--cc=zong@andestech.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