[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAhSdy0uVZXsP1_3zZiwXXEXBZGkmWX5ujptirojD8S4nuzQpQ@mail.gmail.com>
Date: Thu, 4 Jan 2024 17:03:10 +0530
From: Anup Patel <anup@...infault.org>
To: Andrew Jones <ajones@...tanamicro.com>
Cc: Alexandre Ghiti <alex@...ti.fr>, linux-riscv@...ts.infradead.org,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
kvm-riscv@...ts.infradead.org, paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, atishp@...shpatra.org, rdunlap@...radead.org,
sfr@...b.auug.org.au, mpe@...erman.id.au, npiggin@...il.com,
linuxppc-dev@...ts.ozlabs.org, pbonzini@...hat.com
Subject: Re: Re: [PATCH] RISC-V: KVM: Require HAVE_KVM
On Thu, Jan 4, 2024 at 4:51 PM Andrew Jones <ajones@...tanamicro.com> wrote:
>
> On Thu, Jan 04, 2024 at 12:07:51PM +0100, Alexandre Ghiti wrote:
> > On 04/01/2024 11:52, Andrew Jones wrote:
> > > This applies to linux-next, but I forgot to append -next to the PATCH
> > > prefix.
> >
> >
> > Shoudn't this go to -fixes instead? With a Fixes tag?
>
> I'm not sure how urgent it is since it's a randconfig thing, but if we
> think it deserves the -fixes track then I can do that. The Fixes tag isn't
> super easy to select since, while it seems like it should be 8132d887a702
> ("KVM: remove CONFIG_HAVE_KVM_EVENTFD"), it could also be 99cdc6c18c2d
> ("RISC-V: Add initial skeletal KVM support").
>
> I'll leave both the urgency decision and the Fixes tag selection up to
> the maintainers. Anup? Paolo?
Lets add
Fixes: 99cdc6c18c2d ("RISC-V: Add initial skeletal KVM support")
Regards,
Anup
Powered by blists - more mailing lists