From: Pavel Fedin <p.fedin@samsung.com>
To: 'Christoffer Dall' <christoffer.dall@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
'Peter Maydell' <peter.maydell@linaro.org>,
'Marc Zyngier' <marc.zyngier@arm.com>,
'Andre Przywara' <andre.przywara@arm.com>
Subject: RE: [PATCH v4 3/7] KVM: arm/arm64: Fix the documentation
Date: Mon, 12 Oct 2015 10:16:13 +0300 [thread overview]
Message-ID: <016c01d104bd$e1317560$a3946020$@samsung.com> (raw)
In-Reply-To: <20151008082425.GF14315@cbox>
Hello!
> >
> ok, fair enough. This kind of rationale is helpful to put in the commit
> text though.
By the way, may be apply this as a standalone patch? Should i post a standalone version with the
updated commit message then?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-12 7:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 15:27 [PATCH v4 0/7] KVM: arm64: Implement API for vGICv3 live migration Pavel Fedin
2015-09-28 15:27 ` [PATCH v4 1/7] KVM: arm/arm64: Move endianness conversion out of vgic_attr_regs_access() Pavel Fedin
2015-09-28 15:27 ` [PATCH v4 2/7] KVM: arm/arm64: Refactor vGIC attributes handling code Pavel Fedin
2015-09-28 15:27 ` [PATCH v4 3/7] KVM: arm/arm64: Fix the documentation Pavel Fedin
2015-10-07 20:04 ` Christoffer Dall
2015-10-08 6:52 ` Pavel Fedin
2015-10-08 8:24 ` Christoffer Dall
2015-10-12 7:16 ` Pavel Fedin [this message]
2015-10-12 11:56 ` Christoffer Dall
2015-09-28 15:27 ` [PATCH v4 4/7] KVM: arm64: Implement vGICv3 distributor and redistributor access from userspace Pavel Fedin
2015-10-07 20:07 ` Christoffer Dall
2015-09-28 15:27 ` [PATCH v4 5/7] KVM: arm64: Refactor system register handlers Pavel Fedin
2015-09-28 15:27 ` [PATCH v4 6/7] KVM: arm64: Introduce find_reg_by_id() Pavel Fedin
2015-09-28 15:27 ` [PATCH v4 7/7] Implement vGICv3 CPU interface access Pavel Fedin
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='016c01d104bd$e1317560$a3946020$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.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.