From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34515) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqjtS-0001ok-F0 for qemu-devel@nongnu.org; Mon, 26 Oct 2015 11:41:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZqjtN-0004jt-Ev for qemu-devel@nongnu.org; Mon, 26 Oct 2015 11:41:06 -0400 Received: from mail-pa0-x231.google.com ([2607:f8b0:400e:c03::231]:34995) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqjtN-0004ja-AT for qemu-devel@nongnu.org; Mon, 26 Oct 2015 11:41:01 -0400 Received: by pasz6 with SMTP id z6so191662308pas.2 for ; Mon, 26 Oct 2015 08:41:00 -0700 (PDT) Sender: Paolo Bonzini References: <1445853060-24201-1-git-send-email-asmetanin@virtuozzo.com> <1445853060-24201-4-git-send-email-asmetanin@virtuozzo.com> <562DFC9B.4050204@openvz.org> From: Paolo Bonzini Message-ID: <562E4986.4070605@redhat.com> Date: Mon, 26 Oct 2015 16:40:54 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 3/7] linux-headers/kvm: add Hyper-V SynIC irq routing type and struct List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , "Denis V. Lunev" Cc: kvm-devel , Gleb Natapov , QEMU Developers , "virtualization@lists.linux-foundation.org" , Roman Kagan , Andrey Smetanin , Vitaly Kuznetsov , "K. Y. Srinivasan" On 26/10/2015 11:16, Peter Maydell wrote: > On 26 October 2015 at 10:12, Denis V. Lunev 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