From: Andreas Schwab <schwab@linux-m68k.org>
To: guoren@kernel.org
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, Anup.Patel@wdc.com,
vincent.chen@sifive.com, zong.li@sifive.com,
greentime.hu@sifive.com, bmeng.cn@gmail.com, atish.patra@wdc.com,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
arnd@arndb.de, linux-csky@vger.kernel.org,
linux-riscv@lists.infradead.org, Guo Ren <ren_guo@c-sky.com>
Subject: Re: [PATCH 2/2] riscv: Add vector ISA support
Date: Sun, 05 Jan 2020 09:39:23 +0100 [thread overview]
Message-ID: <87o8viwb44.fsf@hase.home> (raw)
In-Reply-To: <20200105025215.2522-2-guoren@kernel.org> (guoren@kernel.org's message of "Sun, 5 Jan 2020 10:52:15 +0800")
On Jan 05 2020, guoren@kernel.org wrote:
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index d8efbaa78d67..3d336f869ffe 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -286,6 +286,15 @@ config FPU
>
> If you don't know what to do here, say Y.
>
> +config VECTOR
> + bool "VECTOR support"
> + default n
default n is the default. Did you mean default y?
> + help
> + Say N here if you want to disable all vecotr related procedure
s/vecotr/vector/
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-01-05 8:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 2:52 [PATCH 1/2] riscv: Fixup obvious bug for fp-regs reset guoren
2020-01-05 2:52 ` [PATCH 2/2] riscv: Add vector ISA support guoren
2020-01-05 8:39 ` Andreas Schwab [this message]
2020-01-05 9:01 ` Guo Ren
2020-01-05 12:32 ` kbuild test robot
2020-01-06 3:27 ` Guo Ren
2020-01-05 16:22 ` kbuild test robot
2020-01-06 2:45 ` Alan Kao
2020-01-06 3:00 ` Anup Patel
2020-01-06 3:38 ` Guo Ren
2020-01-06 3:32 ` Guo Ren
2020-01-06 9:25 ` Anup Patel
2020-01-07 16:15 ` Guo Ren
2020-01-11 1:30 ` [PATCH 1/2] riscv: Fixup obvious bug for fp-regs reset Paul Walmsley
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=87o8viwb44.fsf@hase.home \
--to=schwab@linux-m68k.org \
--cc=Anup.Patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=atish.patra@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ren_guo@c-sky.com \
--cc=vincent.chen@sifive.com \
--cc=zong.li@sifive.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).