From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [PATCH 5/5] Auto-detect whether a FPU exists
Date: Thu, 30 Aug 2018 07:32:23 -0700 [thread overview]
Message-ID: <20180830143223.GB11544@infradead.org> (raw)
In-Reply-To: <1535332075-5727-6-git-send-email-alankao@andestech.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2018-08-30 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 1:07 [PATCH v7 0/5] riscv: Add support to no-FPU systems Alan Kao
2018-08-27 1:07 ` [PATCH 1/5] Extract FPU context operations from entry.S Alan Kao
2018-08-27 1:07 ` [PATCH 2/5] Refactor FPU code in signal setup/return procedures Alan Kao
2018-08-27 1:07 ` [PATCH 3/5] Cleanup ISA string setting Alan Kao
2018-08-30 14:31 ` Christoph Hellwig
2018-08-27 1:07 ` [PATCH 4/5] Allow to disable FPU support Alan Kao
2018-08-27 1:07 ` [PATCH 5/5] Auto-detect whether a FPU exists Alan Kao
2018-08-30 14:32 ` Christoph Hellwig [this message]
2018-09-06 9:45 ` [PATCH v7 0/5] riscv: Add support to no-FPU systems Palmer Dabbelt
2018-10-04 5:30 ` Alan Kao
2018-10-04 5:30 ` Alan Kao
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=20180830143223.GB11544@infradead.org \
--to=hch@infradead.org \
--cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).