From: Christoffer Dall <christoffer.dall@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eric Auger <eric.auger@linaro.org>,
Shlomo Pongratz <shlomo.pongratz@huawei.com>,
Shlomo Pongratz <shlomopongratz@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 4/9] Add virt-v3 machine that uses GIC-500
Date: Fri, 3 Jul 2015 09:42:09 +0200 [thread overview]
Message-ID: <CAMJs5B88kZcbewzPy=7NSJDZg4NK8n75LE2pMLRKc79T8xuGsw@mail.gmail.com> (raw)
In-Reply-To: <006e01d0b55c$dac86810$90593830$@samsung.com>
On Fri, Jul 3, 2015 at 8:52 AM, Pavel Fedin <p.fedin@samsung.com> wrote:
> Hi!
>
>> I think you should leave out the software emulation part for this
>> series and let's concentrate on getting this in first.
>
> Ok.
>
>> Also, you should make sure you have an agreement with Shlomo about
>> taking over his patches before doing so (maybe you are already?).
>
> Shlomo has posted his work here, doesn't this automatically mean that he is sharing it with the community? Additionally, i do not drop his authorship.
>
Well, it can become a little messy for everyone if Shlomo is working
on refactoring and respinning his patches, and meanwhile new versions
of his patches go out embedded as part of another patch set. It's not
exactly harmful, but usually doesn't happen without prior agreement
amongst the involved parties, I would say.
-Christoffer
next prev parent reply other threads:[~2015-07-03 7:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 14:13 [Qemu-devel] [PATCH v4 0/9] GIC-500 implementation, software + KVM Pavel Fedin
2015-07-02 14:13 ` [Qemu-devel] [PATCH v4 1/9] Implement GIC-500 base class Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 2/9] Implement GIC-500 Pavel Fedin
2015-07-02 14:19 ` Peter Maydell
2015-07-02 14:39 ` Pavel Fedin
2015-07-02 14:42 ` Peter Maydell
2015-07-02 14:45 ` Peter Maydell
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 3/9] GICv3 support Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 4/9] Add virt-v3 machine that uses GIC-500 Pavel Fedin
2015-07-02 14:25 ` Daniel P. Berrange
2015-07-02 14:47 ` Pavel Fedin
2015-07-02 15:06 ` Christoffer Dall
2015-07-02 15:30 ` Pavel Fedin
2015-07-02 15:54 ` Christoffer Dall
2015-07-03 6:52 ` Pavel Fedin
2015-07-03 7:42 ` Christoffer Dall [this message]
2015-07-03 8:47 ` Pavel Fedin
2015-07-03 10:23 ` Christoffer Dall
2015-07-02 16:21 ` Daniel P. Berrange
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 5/9] Extract some reusable vGIC code Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 6/9] Set kernel_irqchip_type for the rest of ARM boards which use GIC Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 7/9] Make use of kernel_irqchip_type in kvm_arch_irqchip_create() Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 8/9] Initial implementation of vGICv3 Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 9/9] Enable KVM acceleration for GICv3 Pavel Fedin
2015-07-07 10:20 ` [Qemu-devel] [PATCH v4 0/9] GIC-500 implementation, software + KVM Eric Auger
2015-07-07 12:45 ` Pavel Fedin
2015-07-07 13:27 ` Eric Auger
2015-07-07 14:15 ` 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='CAMJs5B88kZcbewzPy=7NSJDZg4NK8n75LE2pMLRKc79T8xuGsw@mail.gmail.com' \
--to=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shlomo.pongratz@huawei.com \
--cc=shlomopongratz@gmail.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).