From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
"Denis V. Lunev" <den@openvz.org>
Cc: kvm-devel <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
QEMU Developers <qemu-devel@nongnu.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
Roman Kagan <rkagan@virtuozzo.com>,
Andrey Smetanin <asmetanin@virtuozzo.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
"K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [Qemu-devel] [PATCH 3/7] linux-headers/kvm: add Hyper-V SynIC irq routing type and struct
Date: Mon, 26 Oct 2015 16:40:54 +0100 [thread overview]
Message-ID: <562E4986.4070605@redhat.com> (raw)
In-Reply-To: <CAFEAcA_SwJvN8E_6fCawJnwqM3RaB94XGn9TkU7f2VPg40uo-g@mail.gmail.com>
On 26/10/2015 11:16, Peter Maydell wrote:
> On 26 October 2015 at 10:12, Denis V. Lunev <den@openvz.org> wrote:
>> On 10/26/2015 01:03 PM, Peter Maydell wrote:
>>> Hi. Changes to linux-headers/ should only be made as part of
>>> an automated update from a mainline Linux kernel tree using
>>> the scripts/update-linux-headers.sh script. This patch looks
>>> like maybe it was a manual edit ?
>
>> yep. We know and have discussed this with Paolo already.
>> Kernel stuff is in progress at the moment. The patch
>> is presented to interested people to allow to compile and
>> run.
>>
>> Actual merge will be performed with proper sync
>> when kernel will be in rc3 or 4 stage and the patch will be
>> dropped.
>
> OK, cool. It's best to tag the series as 'RFC' rather than
> 'PATCH' in that case, as a reminder that it can't be applied
> just yet.
I'm still going to apply it to a branch for now, so it's not strictly
RFC. I'm not sending a pull request, however, until I rebase the
branch, and then it will just go away.
Paolo
next prev parent reply other threads:[~2015-10-26 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 9:50 [Qemu-devel] [PATCH 0/7] Hyper-V Synthetic interrupt controller Andrey Smetanin
2015-10-26 9:50 ` [Qemu-devel] [PATCH 1/7] standard-headers/x86: add Hyper-V SynIC constants Andrey Smetanin
2015-10-26 9:50 ` [Qemu-devel] [PATCH 2/7] target-i386/kvm: Hyper-V SynIC MSR's support Andrey Smetanin
2015-10-26 9:50 ` [Qemu-devel] [PATCH 3/7] linux-headers/kvm: add Hyper-V SynIC irq routing type and struct Andrey Smetanin
2015-10-26 10:03 ` Peter Maydell
2015-10-26 10:12 ` Denis V. Lunev
2015-10-26 10:16 ` Peter Maydell
2015-10-26 15:40 ` Paolo Bonzini [this message]
2015-10-26 9:50 ` [Qemu-devel] [PATCH 4/7] kvm: Hyper-V SynIC irq routing support Andrey Smetanin
2015-10-26 9:50 ` [Qemu-devel] [PATCH 5/7] linux-headers/kvm: KVM_EXIT_HYPERV type and struct Andrey Smetanin
2015-10-26 9:50 ` [Qemu-devel] [PATCH 6/7] target-i386/hyperv: Hyper-V SynIC SINT routing and vCPU exit Andrey Smetanin
2015-10-26 9:51 ` [Qemu-devel] [PATCH 7/7] hw/misc: Hyper-V test device 'hyperv-testdev' Andrey Smetanin
2015-11-02 11:55 ` [Qemu-devel] [PATCH 0/7] Hyper-V Synthetic interrupt controller Paolo Bonzini
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=562E4986.4070605@redhat.com \
--to=pbonzini@redhat.com \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vkuznets@redhat.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).