From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oupton@google.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org,
Peter Shier <pshier@google.com>,
Ricardo Koller <ricarkol@google.com>,
Reiji Watanabe <reijiw@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 2/2] Documentation: KVM: Move KVM/arm64 docs into aptly named directory
Date: Thu, 03 Mar 2022 07:28:02 +0000 [thread overview]
Message-ID: <87pmn35wcd.wl-maz@kernel.org> (raw)
In-Reply-To: <20220302194221.1774513-3-oupton@google.com>
On Wed, 02 Mar 2022 19:42:21 +0000,
Oliver Upton <oupton@google.com> wrote:
>
> ARM64 is the only supported ARM archiecture for KVM now. Move all the
> documentation into a new directory, arm64, making the file structure
> consistent with this change.
>
> While we're at it, rename hyp-abi.rst to el2-abi.rst for the sake of
> consistency with the architecture as well.
See my earlier comment as to why this isn't valid. As for the rest of
the renaming, I'm not opposed to it, but it doesn't bring a lot either.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-03-03 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 19:42 [PATCH 0/2] KVM: arm: Drop documentation of 32-bit KVM Oliver Upton
2022-03-02 19:42 ` [PATCH 1/2] Documentation: KVM: Update documentation to indicate KVM is arm64-only Oliver Upton
2022-03-03 7:21 ` Marc Zyngier
2022-03-02 19:42 ` [PATCH 2/2] Documentation: KVM: Move KVM/arm64 docs into aptly named directory Oliver Upton
2022-03-03 7:28 ` Marc Zyngier [this message]
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=87pmn35wcd.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.com \
--cc=reijiw@google.com \
--cc=ricarkol@google.com \
--cc=suzuki.poulose@arm.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).