From: Will Deacon <will@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: maz@kernel.org, kvmarm@lists.cs.columbia.edu, catalin.marinas@arm.com
Subject: Re: [PATCH v4 4/4] KVM: arm64: Clean up kvm makefiles
Date: Thu, 30 Apr 2020 21:25:10 +0100 [thread overview]
Message-ID: <20200430202509.GA31455@willie-the-truck> (raw)
In-Reply-To: <20200421131734.141766-5-tabba@google.com>
On Tue, Apr 21, 2020 at 02:17:34PM +0100, Fuad Tabba wrote:
> Consolidate references to the CONFIG_KVM configuration item to encompass
> entire folders rather than per line.
>
> Signed-off-by: Fuad Tabba <tabba@google.com>
> ---
> arch/arm64/kvm/Makefile | 40 ++++++++++++-------------------------
> arch/arm64/kvm/hyp/Makefile | 15 ++++----------
> 2 files changed, 17 insertions(+), 38 deletions(-)
Seems like a sensible clean-up to me:
Acked-by: Will Deacon <will@kernel.org>
Will
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-04-30 20:25 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
2020-04-21 13:17 ` [PATCH v4 4/4] KVM: arm64: Clean up kvm makefiles Fuad Tabba
2020-04-30 20:25 ` Will Deacon [this message]
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=20200430202509.GA31455@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.org \
--cc=tabba@google.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).