public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Andrew Jones <ajones@ventanamicro•com>
To: Alexandre Ghiti <alex@ghiti•fr>
Cc: linux-riscv@lists•infradead.org, linux-next@vger•kernel.org,
	 linux-kernel@vger•kernel.org, kvm@vger•kernel.org,
	kvm-riscv@lists•infradead.org,  paul.walmsley@sifive•com,
	palmer@dabbelt•com, aou@eecs•berkeley.edu, anup@brainfault•org,
	 atishp@atishpatra•org, rdunlap@infradead•org,
	sfr@canb•auug.org.au, mpe@ellerman•id.au,  npiggin@gmail•com,
	linuxppc-dev@lists•ozlabs.org, pbonzini@redhat•com
Subject: Re: Re: [PATCH] RISC-V: KVM: Require HAVE_KVM
Date: Thu, 4 Jan 2024 12:21:05 +0100	[thread overview]
Message-ID: <20240104-6a5a59dde14adcaf3ac22a35@orel> (raw)
In-Reply-To: <752c11ea-7172-40ff-a821-c78aeb6c5518@ghiti.fr>

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?

Thanks,
drew

next prev parent reply	other threads:[~2024-01-04 11:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 10:43 [PATCH] RISC-V: KVM: Require HAVE_KVM Andrew Jones
2024-01-04 10:52 ` Andrew Jones
2024-01-04 11:07   ` Alexandre Ghiti
2024-01-04 11:21     ` Andrew Jones [this message]
2024-01-04 11:33       ` Anup Patel

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=20240104-6a5a59dde14adcaf3ac22a35@orel \
    --to=ajones@ventanamicro$(echo .)com \
    --cc=alex@ghiti$(echo .)fr \
    --cc=anup@brainfault$(echo .)org \
    --cc=aou@eecs$(echo .)berkeley.edu \
    --cc=atishp@atishpatra$(echo .)org \
    --cc=kvm-riscv@lists$(echo .)infradead.org \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-riscv@lists$(echo .)infradead.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=npiggin@gmail$(echo .)com \
    --cc=palmer@dabbelt$(echo .)com \
    --cc=paul.walmsley@sifive$(echo .)com \
    --cc=pbonzini@redhat$(echo .)com \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox