All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Andre Przywara <andre.przywara@arm.com>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	arm-mail-list <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation
Date: Thu, 8 Oct 2015 11:25:41 +0100	[thread overview]
Message-ID: <CAFEAcA-3vUgB=LCsiEwGoM0G28yszw+90LFajOB8akgwiQwuuw@mail.gmail.com> (raw)
In-Reply-To: <005e01d101a9$31ee80f0$95cb82d0$@samsung.com>

On 8 October 2015 at 10:10, Pavel Fedin <p.fedin@samsung.com> wrote:
>  Sorry, didn't want to offend anyone. I just wanted to tell that i know
> that you, as maintainers, have much more power than i do, and you can
> always say "it's political decision, we just want it and that's final",
> and if you choose to do this, i'm perfectly OK with that, just say it.

This isn't intended to be a political decision; it's our joint
technical opinion on the best design for this API. Since we all
happened to be in one physical location the other week it was a good
opportunity for us to work through how we thought the API should
look from a technical perspective. At that point it seemed to us
to be clearer to write up the results of that discussion as a
single patch to the API documentation, rather than doing it by
(for instance) making lots of different review comments on your patches.
Christoffer's API documentation patch is a patch like any other and
it has to go through review. If there are parts where you don't
understand the rationale or you think we got something wrong you
should let us know.

thanks
-- PMM

WARNING: multiple messages have this Message-ID (diff)
From: peter.maydell@linaro.org (Peter Maydell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation
Date: Thu, 8 Oct 2015 11:25:41 +0100	[thread overview]
Message-ID: <CAFEAcA-3vUgB=LCsiEwGoM0G28yszw+90LFajOB8akgwiQwuuw@mail.gmail.com> (raw)
In-Reply-To: <005e01d101a9$31ee80f0$95cb82d0$@samsung.com>

On 8 October 2015 at 10:10, Pavel Fedin <p.fedin@samsung.com> wrote:
>  Sorry, didn't want to offend anyone. I just wanted to tell that i know
> that you, as maintainers, have much more power than i do, and you can
> always say "it's political decision, we just want it and that's final",
> and if you choose to do this, i'm perfectly OK with that, just say it.

This isn't intended to be a political decision; it's our joint
technical opinion on the best design for this API. Since we all
happened to be in one physical location the other week it was a good
opportunity for us to work through how we thought the API should
look from a technical perspective. At that point it seemed to us
to be clearer to write up the results of that discussion as a
single patch to the API documentation, rather than doing it by
(for instance) making lots of different review comments on your patches.
Christoffer's API documentation patch is a patch like any other and
it has to go through review. If there are parts where you don't
understand the rationale or you think we got something wrong you
should let us know.

thanks
-- PMM

  parent reply	other threads:[~2015-10-08 10:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 19:50 [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation Christoffer Dall
2015-10-07 19:50 ` Christoffer Dall
2015-10-08  7:17 ` Pavel Fedin
2015-10-08  7:17   ` Pavel Fedin
2015-10-08  8:23   ` Christoffer Dall
2015-10-08  8:23     ` Christoffer Dall
2015-10-08  9:10     ` Pavel Fedin
2015-10-08  9:10       ` Pavel Fedin
2015-10-08  9:28       ` Christoffer Dall
2015-10-08  9:28         ` Christoffer Dall
2015-10-08 10:14         ` Marc Zyngier
2015-10-08 10:14           ` Marc Zyngier
2015-10-08 12:28           ` Pavel Fedin
2015-10-08 12:28             ` Pavel Fedin
2015-10-08 12:36             ` Christoffer Dall
2015-10-08 12:36               ` Christoffer Dall
2015-10-08 12:45               ` Pavel Fedin
2015-10-08 12:45                 ` Pavel Fedin
2015-10-08 12:51                 ` Marc Zyngier
2015-10-08 12:51                   ` Marc Zyngier
2015-10-08 12:55                 ` Peter Maydell
2015-10-08 12:55                   ` Peter Maydell
2015-10-08 13:28                   ` [Qemu-devel] " Pavel Fedin
2015-10-08 13:37                     ` Peter Maydell
2015-10-08 14:29                       ` Pavel Fedin
2015-10-08 10:25       ` Peter Maydell [this message]
2015-10-08 10:25         ` Peter Maydell
2015-10-09  7:30 ` Pavel Fedin
2015-10-09  7:30   ` Pavel Fedin
2015-10-09  8:06   ` Marc Zyngier
2015-10-09  8:06     ` Marc Zyngier
2015-10-09  8:10     ` Pavel Fedin
2015-10-09  8:10       ` Pavel Fedin
2015-10-09  8:29       ` Marc Zyngier
2015-10-09  8:29         ` Marc Zyngier

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='CAFEAcA-3vUgB=LCsiEwGoM0G28yszw+90LFajOB8akgwiQwuuw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=andre.przywara@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    --cc=p.fedin@samsung.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 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.