[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAhSdy0J7WVJO5vbz1JeHChitbJpagyuE1nF8XHfY-K=DnySGg@mail.gmail.com>
Date: Tue, 4 Jan 2022 19:29:58 +0530
From: Anup Patel <anup@...infault.org>
To: Heiko Stübner <heiko@...ech.de>
Cc: "linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Atish Patra <atishp@...osinc.com>,
Albert Ou <aou@...s.berkeley.edu>,
Heinrich Schuchardt <xypron.glpk@....de>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
kvm-riscv@...ts.infradead.org, KVM General <kvm@...r.kernel.org>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>
Subject: Re: [PATCH v5 1/5] RISC-V: KVM: Mark the existing SBI implementation
as v01
On Tue, Jan 4, 2022 at 6:57 PM Heiko Stübner <heiko@...ech.de> wrote:
>
> Am Dienstag, 4. Januar 2022, 14:19:41 CET schrieb Heiko Stübner:
> > Hi Atish,
> >
> > Am Donnerstag, 18. November 2021, 09:39:08 CET schrieb Atish Patra:
> > > From: Atish Patra <atish.patra@....com>
> > >
> > > The existing SBI specification impelementation follows v0.1
> > > specification. The latest specification allows more
> > > scalability and performance improvements.
> > >
> > > Rename the existing implementation as v01 and provide a way to allow
> > > future extensions.
> > >
> > > Reviewed-by: Anup Patel <anup.patel@....com>
> > > Signed-off-by: Atish Patra <atish.patra@....com>
> > > Signed-off-by: Atish Patra <atishp@...osinc.com>
> > > ---
> >
> > > diff --git a/arch/riscv/kvm/vcpu_sbi.c b/arch/riscv/kvm/vcpu_sbi.c
> > > index eb3c045edf11..32376906ff20 100644
> > > --- a/arch/riscv/kvm/vcpu_sbi.c
> > > +++ b/arch/riscv/kvm/vcpu_sbi.c
> > > @@ -1,5 +1,5 @@
> > > // SPDX-License-Identifier: GPL-2.0
> > > -/**
> > > +/*
> > > * Copyright (c) 2019 Western Digital Corporation or its affiliates.
> > > *
> > > * Authors:
> >
> > This got already fixed by [0]
> > commit 0e2e64192100 ("riscv: kvm: fix non-kernel-doc comment block")
> > so this patch doesn't apply cleanly anymore.
>
> hmm, just found Anup's "I've queued this..." message after
> writing my reply, so scratch the above ;-) .
>
> @Anup: I've looked at git.kernel.org but didn't find a tree
> there, can you tell me where this did go to?
All queued patches are in riscv_kvm_queue branch of
the KVM RISC-V tree at https://github.com/kvm-riscv/linux.git
Regards,
Anup
>
> Thanks
> Heiko
>
>
Powered by blists - more mailing lists