linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Anup Patel <anup@brainfault.org>,
	Palmer Dabbelt <palmerdabbelt@google.com>,
	Albert Ou <aou@eecs.berkeley.edu>, Gary Guo <gary@garyguo.net>,
	Greentime Hu <greentime.hu@sifive.com>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	Mao Han <han_mao@c-sky.com>, Mike Rapoport <rppt@linux.ibm.com>,
	Nick Hu <nickhu@andestech.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vincent Chen <vincent.chen@sifive.com>,
	Zong Li <zong.li@sifive.com>
Subject: Re: [PATCH v11 01/11] RISC-V: Mark existing SBI as 0.1 SBI.
Date: Sun, 5 Apr 2020 22:36:50 +0800	[thread overview]
Message-ID: <CAEUhbmW3tkOxu99VHhMCOSFoonp7Z9TuNsN22JBhYT7a+2vk8A@mail.gmail.com> (raw)
In-Reply-To: <20200318011144.91532-2-atish.patra@wdc.com>

On Wed, Mar 18, 2020 at 9:11 AM Atish Patra <atish.patra@wdc.com> wrote:
>
> As per the new SBI specification, current SBI implementation version
> is defined as 0.1 and will be removed/replaced in future. Each of the
> function call in 0.1 is defined as a separate extension which makes
> easier to replace them one at a time.
>
> Rename existing implementation to reflect that. This patch is just
> a preparatory patch for SBI v0.2 and doesn't introduce any functional
> changes.
>

nits: remove the ending period in the commit title

> Signed-off-by: Atish Patra <atish.patra@wdc.com>
> Reviewed-by: Anup Patel <anup@brainfault.org>
> Reviewed-by: Palmer Dabbelt <palmerdabbelt@google.com>
> ---
>  arch/riscv/include/asm/sbi.h | 41 +++++++++++++++++++-----------------
>  1 file changed, 22 insertions(+), 19 deletions(-)

[snip]

Other than that,
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>

  reply	other threads:[~2020-04-05 14:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  1:11 [PATCH v11 00/11] Add support for SBI v0.2 and CPU hotplug Atish Patra
2020-03-18  1:11 ` [PATCH v11 01/11] RISC-V: Mark existing SBI as 0.1 SBI Atish Patra
2020-04-05 14:36   ` Bin Meng [this message]
2020-03-18  1:11 ` [PATCH v11 02/11] RISC-V: Add basic support for SBI v0.2 Atish Patra
2020-04-05 14:36   ` Bin Meng
2020-03-18  1:11 ` [PATCH v11 03/11] RISC-V: Add SBI v0.2 extension definitions Atish Patra
2020-04-05 14:37   ` Bin Meng
2020-03-18  1:11 ` [PATCH v11 04/11] RISC-V: Introduce a new config for SBI v0.1 Atish Patra
2020-04-05 14:37   ` Bin Meng
2020-03-18  1:11 ` [PATCH v11 05/11] RISC-V: Implement new SBI v0.2 extensions Atish Patra
2020-04-05 14:37   ` Bin Meng
2020-03-18  1:11 ` [PATCH v11 06/11] RISC-V: Move relocate and few other functions out of __init Atish Patra
2020-03-18  1:11 ` [PATCH v11 07/11] RISC-V: Add cpu_ops and modify default booting method Atish Patra
2020-03-18  1:11 ` [PATCH v11 08/11] RISC-V: Export SBI error to linux error mapping function Atish Patra
2020-04-05 14:37   ` Bin Meng
2020-03-18  1:11 ` [PATCH v11 09/11] RISC-V: Add SBI HSM extension definitions Atish Patra
2020-04-05 14:37   ` Bin Meng
2020-03-18  1:11 ` [PATCH v11 10/11] RISC-V: Add supported for ordered booting method using HSM Atish Patra
2020-04-05 14:37   ` Bin Meng
2020-03-18  1:11 ` [PATCH v11 11/11] RISC-V: Support cpu hotplug Atish Patra
2020-03-31 18:35   ` Palmer Dabbelt
2020-03-22 17:49 ` [PATCH v11 00/11] Add support for SBI v0.2 and CPU hotplug Emil Renner Berthing
2020-03-23  3:03   ` Atish Patra
2020-03-31 18:35 ` Palmer Dabbelt
2020-04-01  0:43   ` Atish Patra

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=CAEUhbmW3tkOxu99VHhMCOSFoonp7Z9TuNsN22JBhYT7a+2vk8A@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@wdc.com \
    --cc=gary@garyguo.net \
    --cc=greentime.hu@sifive.com \
    --cc=han_mao@c-sky.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=nickhu@andestech.com \
    --cc=palmer@dabbelt.com \
    --cc=palmerdabbelt@google.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rppt@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --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).