From: Alan Kao <alankao@andestech.com>
To: guoren@kernel.org
Cc: linux-arch@vger.kernel.org, aou@eecs.berkeley.edu,
Guo Ren <ren_guo@c-sky.com>,
arnd@arndb.de, atish.patra@wdc.com, Anup.Patel@wdc.com,
linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
vincent.chen@sifive.com, palmer@dabbelt.com, zong.li@sifive.com,
paul.walmsley@sifive.com, greentime.hu@sifive.com,
linux-riscv@lists.infradead.org, bmeng.cn@gmail.com
Subject: Re: [PATCH 2/2] riscv: Add vector ISA support
Date: Mon, 6 Jan 2020 10:45:16 +0800 [thread overview]
Message-ID: <20200106024515.GA1021@andestech.com> (raw)
In-Reply-To: <20200105025215.2522-2-guoren@kernel.org>
Hi Guo,
On Sun, Jan 05, 2020 at 10:52:15AM +0800, guoren@kernel.org wrote:
> From: Guo Ren <ren_guo@c-sky.com>
>
> The implementation follow the RISC-V "V" Vector Extension draft v0.8 with
> 128bit-vlen and it's based on linux-5.5-rc4.
>
According to https://lkml.org/lkml/2019/11/22/2169, in which Paul has stated
that "we plan to only accept patches for new modules or extensions that have
been frozen or ratified by the RISC-V Foundation."
Is v0.8 ratified enough for now?
WARNING: multiple messages have this Message-ID (diff)
From: Alan Kao <alankao@andestech.com>
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-arch@vger.kernel.org>,
<arnd@arndb.de>, <linux-kernel@vger.kernel.org>,
<linux-csky@vger.kernel.org>, Guo Ren <ren_guo@c-sky.com>,
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 2/2] riscv: Add vector ISA support
Date: Mon, 6 Jan 2020 10:45:16 +0800 [thread overview]
Message-ID: <20200106024515.GA1021@andestech.com> (raw)
In-Reply-To: <20200105025215.2522-2-guoren@kernel.org>
Hi Guo,
On Sun, Jan 05, 2020 at 10:52:15AM +0800, guoren@kernel.org wrote:
> From: Guo Ren <ren_guo@c-sky.com>
>
> The implementation follow the RISC-V "V" Vector Extension draft v0.8 with
> 128bit-vlen and it's based on linux-5.5-rc4.
>
According to https://lkml.org/lkml/2019/11/22/2169, in which Paul has stated
that "we plan to only accept patches for new modules or extensions that have
been frozen or ratified by the RISC-V Foundation."
Is v0.8 ratified enough for now?
WARNING: multiple messages have this Message-ID (diff)
From: Alan Kao <alankao@andestech.com>
To: <guoren@kernel.org>
Cc: linux-arch@vger.kernel.org, aou@eecs.berkeley.edu,
Guo Ren <ren_guo@c-sky.com>,
arnd@arndb.de, atish.patra@wdc.com, Anup.Patel@wdc.com,
linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
vincent.chen@sifive.com, palmer@dabbelt.com, zong.li@sifive.com,
paul.walmsley@sifive.com, greentime.hu@sifive.com,
linux-riscv@lists.infradead.org, bmeng.cn@gmail.com
Subject: Re: [PATCH 2/2] riscv: Add vector ISA support
Date: Mon, 6 Jan 2020 10:45:16 +0800 [thread overview]
Message-ID: <20200106024515.GA1021@andestech.com> (raw)
In-Reply-To: <20200105025215.2522-2-guoren@kernel.org>
Hi Guo,
On Sun, Jan 05, 2020 at 10:52:15AM +0800, guoren@kernel.org wrote:
> From: Guo Ren <ren_guo@c-sky.com>
>
> The implementation follow the RISC-V "V" Vector Extension draft v0.8 with
> 128bit-vlen and it's based on linux-5.5-rc4.
>
According to https://lkml.org/lkml/2019/11/22/2169, in which Paul has stated
that "we plan to only accept patches for new modules or extensions that have
been frozen or ratified by the RISC-V Foundation."
Is v0.8 ratified enough for now?
next prev parent reply other threads:[~2020-01-06 2:45 UTC|newest]
Thread overview: 32+ 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 ` guoren
2020-01-05 2:52 ` [PATCH 2/2] riscv: Add vector ISA support guoren
2020-01-05 2:52 ` guoren
2020-01-05 8:39 ` Andreas Schwab
2020-01-05 8:39 ` Andreas Schwab
2020-01-05 9:01 ` Guo Ren
2020-01-05 9:01 ` Guo Ren
2020-01-05 12:32 ` kbuild test robot
2020-01-05 12:32 ` kbuild test robot
2020-01-05 12:32 ` kbuild test robot
2020-01-06 3:27 ` Guo Ren
2020-01-06 3:27 ` Guo Ren
2020-01-06 3:27 ` Guo Ren
2020-01-05 16:22 ` kbuild test robot
2020-01-05 16:22 ` kbuild test robot
2020-01-05 16:22 ` kbuild test robot
2020-01-06 2:45 ` Alan Kao [this message]
2020-01-06 2:45 ` Alan Kao
2020-01-06 2:45 ` Alan Kao
2020-01-06 3:00 ` Anup Patel
2020-01-06 3:00 ` Anup Patel
2020-01-06 3:38 ` Guo Ren
2020-01-06 3:38 ` Guo Ren
2020-01-06 3:32 ` Guo Ren
2020-01-06 3:32 ` Guo Ren
2020-01-06 9:25 ` Anup Patel
2020-01-06 9:25 ` Anup Patel
2020-01-07 16:15 ` Guo Ren
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
2020-01-11 1:30 ` 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=20200106024515.GA1021@andestech.com \
--to=alankao@andestech.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.