All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: tabba@google.com, maz@kernel.org, catalin.marinas@arm.com,
	julien.thierry.kdev@gmail.com, kvmarm@lists.cs.columbia.edu
Cc: will@kernel.org
Subject: Re: [PATCH v4 3/4] KVM: arm64: Change CONFIG_KVM to a menuconfig entry
Date: Fri, 1 May 2020 10:18:03 +0100	[thread overview]
Message-ID: <eda929c3-e55c-74c7-eb0e-e2177aec799d@arm.com> (raw)
In-Reply-To: <20200421131734.141766-4-tabba@google.com>

On 04/21/2020 02:17 PM, Fuad Tabba wrote:
> From: Will Deacon <will@kernel.org>
> 
> Changing CONFIG_KVM to be a 'menuconfig' entry in Kconfig mean that we
> can straightforwardly enumerate optional features, such as the virtual
> PMU device as dependent options.
> 
> Signed-off-by: Will Deacon <will@kernel.org>
> Signed-off-by: Fuad Tabba <tabba@google.com>

Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com>
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2020-05-01  9:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:17 [PATCH v4 0/4] KVM: arm64: Tidy up arch Kconfig and Makefiles Fuad Tabba
2020-04-21 13:17 ` [PATCH v4 1/4] KVM: arm64: Kill off CONFIG_KVM_ARM_HOST Fuad Tabba
2020-05-01  9:16   ` Suzuki K Poulose
2020-04-21 13:17 ` [PATCH v4 2/4] KVM: arm64: Update help text Fuad Tabba
2020-05-01  8:56   ` Suzuki K Poulose
2020-04-21 13:17 ` [PATCH v4 3/4] KVM: arm64: Change CONFIG_KVM to a menuconfig entry Fuad Tabba
2020-05-01  9:18   ` Suzuki K Poulose [this message]
2020-04-21 13:17 ` [PATCH v4 4/4] KVM: arm64: Clean up kvm makefiles Fuad Tabba
2020-04-30 20:25   ` Will Deacon
2020-05-04 13:26   ` Quentin Perret
2020-05-04 15:27     ` Marc Zyngier
2020-05-04 15:29       ` Fuad Tabba

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=eda929c3-e55c-74c7-eb0e-e2177aec799d@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=julien.thierry.kdev@gmail.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=maz@kernel.org \
    --cc=tabba@google.com \
    --cc=will@kernel.org \
    /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.