From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.4 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,T_DKIM_INVALID,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by aws-us-west-2-korg-lkml-1.web.codeaurora.org (Postfix) with ESMTP id 4E563C433EF for ; Wed, 13 Jun 2018 06:25:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E95172086A for ; Wed, 13 Jun 2018 06:25:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Pl9g9RJp" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E95172086A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754489AbeFMGZZ (ORCPT ); Wed, 13 Jun 2018 02:25:25 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:33243 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754377AbeFMGZX (ORCPT ); Wed, 13 Jun 2018 02:25:23 -0400 Received: by mail-pf0-f194.google.com with SMTP id b17-v6so843824pfi.0; Tue, 12 Jun 2018 23:25:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:cc:from:message-id; bh=jhr/ACJNLvVA7liZnsR38q8LQYJ/QHvBnSDMriT5EBM=; b=Pl9g9RJpcdrlwCciTovZja6XPNJBWKlPez8rHKeK+5FzoHQaLMoRp+eKoGNmllQvRJ Qoyq7jDJAhG+XMVT/lmHxDEhgHKmh1DcCYpeoON8/GRATKjgJjB+m6dCug7Z8rdsroXH yia/OwR0HWJTPH4Cutkq3xyBSXSLyuar4WXcJFSmZIS7HWcbPE54wDUbYDMXgg5JspKd HLfWcSdP5DXXMyS/6KaPQJJXyhBQZIl8UdB+MGe1+06yVRCKlFEE11ykNghmVLLlMnIa O49ONJGIOKeWjkGAMhFpebMEhbLhAYS+aYIryta03tDk8DMPWqJIWowjX6BmJb0yVOv0 ++yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:cc:from :message-id; bh=jhr/ACJNLvVA7liZnsR38q8LQYJ/QHvBnSDMriT5EBM=; b=LjNXg2mtXsYXwY2Jlvs7MdqMgzKerRmSMvga7M8grnl//5LwEj+Xg8iS5dZ1lV1m4g 8Dbh14XOxGauKmVhurY6PfdFuIz0vQyrQ8XY3hqUla2uJcp2z6fjvDgrqbh8WipfRV05 NXsIF+RJg0iSz5qRlK/0CEPHRY2P9kgQRCE54wUox8enUzWZfgXNsewr3ArpPkzHKwJq m7qjg9VZYyT0EMLeE3iXjMcW9AWJloLot1kF3mYiL1a3T7qxaetT32Mct1GBt1drfzHH vO1rV4im7S9Ov391gGp5uSKISrqAKo2T9Xd02GxNogsRBWYceGcx/w7IPH3KDuSdi85f ke9Q== X-Gm-Message-State: APt69E16xIY49TtOA/Z4GnR5ahP26Sfb7n7a0ueZTNYiv+KETkiF/ng/ ujqWJVmjuCFqw+B1yTiCNc8= X-Google-Smtp-Source: ADUXVKI7FCJtotZ6YVShK8U0EjUaAKreHRmnFs9MrLUGxMoUHxfAnlHcj4yevWmnCkb7Kx0x2wNQXg== X-Received: by 2002:a62:211a:: with SMTP id h26-v6mr3556648pfh.133.1528871122565; Tue, 12 Jun 2018 23:25:22 -0700 (PDT) Received: from ?IPv6:2601:647:4001:5a00:74b5:73d5:5f92:bd10? ([2601:647:4001:5a00:74b5:73d5:5f92:bd10]) by smtp.gmail.com with ESMTPSA id q24-v6sm2766942pfh.26.2018.06.12.23.25.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Jun 2018 23:25:21 -0700 (PDT) Date: Tue, 12 Jun 2018 23:25:17 -0700 User-Agent: K-9 Mail for Android In-Reply-To: References: <20180612074856.28451-1-andr2000@gmail.com> <20180612074856.28451-2-andr2000@gmail.com> <9c579567-ebe2-f465-5443-b3a3e71d34a5@suse.com> <20180612234020.GI38773@dtor-ws> <3605901d-4a72-3f5a-6d74-cb13d2414a0b@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH v5 1/3] xen: Sync up with the canonical protocol definitions in Xen To: Oleksandr Andrushchenko , Juergen Gross CC: xen-devel@lists.xenproject.org, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, lyan@suse.com, boris.ostrovsky@oracle.com, konrad.wilk@oracle.com, andrii_chepurnyi@epam.com, Oleksandr Andrushchenko From: Dmitry Torokhov Message-ID: <800B1B3B-795F-4D0D-8B61-B66FC77A11A8@gmail.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On June 12, 2018 11:13:40 PM PDT, Oleksandr Andrushchenko wrote: >On 06/13/2018 09:11 AM, Dmitry Torokhov wrote: >> On June 12, 2018 10:49:31 PM PDT, Oleksandr Andrushchenko > wrote: >>> On 06/13/2018 02:40 AM, Dmitry Torokhov wrote: >>>> On Tue, Jun 12, 2018 at 03:46:10PM +0200, Juergen Gross wrote: >>>>> On 12/06/18 09:48, Oleksandr Andrushchenko wrote: >>>>>> From: Oleksandr Andrushchenko >>>>>> >>>>>> This is the sync up with the canonical definitions of the input, >>>>>> sound and display protocols in Xen=2E >>>>>> >>>>>> Changes to kbdif: >>>>>> 1=2E Add missing string constants for {feature|request}-raw-pointer >>>>>> to align with the rest of the interface file=2E >>>>>> >>>>>> 2=2E Add new XenStore feature fields, so it is possible to >>> individually >>>>>> control set of exposed virtual devices for each guest OS: >>>>>> - set feature-disable-keyboard to 1 if no keyboard device >>> needs >>>>>> to be created >>>>>> - set feature-disable-pointer to 1 if no pointer device >needs >>>>>> to be created >>>>>> >>>>>> 3=2E Move multi-touch device parameters to backend nodes: these are >>>>>> described as a part of frontend's XenBus configuration >nodes >>>>>> while they belong to backend's configuration=2E Fix this by >>> moving >>>>>> the parameters to the proper section=2E >>>>>> >>>>>> Unique-id field: >>>>>> 1=2E Add unique-id XenBus entry for virtual input and display=2E >>>>>> >>>>>> 2=2E Change type of unique-id field to string for sndif to align >with >>>>>> display and input protocols=2E >>>>>> >>>>>> Signed-off-by: Oleksandr Andrushchenko >>> >>>>>> Cc: Konrad Rzeszutek Wilk >>>>> Reviewed-by: Juergen Gross >>>>> >>>>> I'm fine with this patch being added via the input tree with the >>> other >>>>> patches=2E In case I should take it via the Xen tree, please send me >a >>>>> note=2E >>>> Juergen, >>>> >>>> I created an immutable branch off v4=2E17 with these 3 patches in >case >>> you >>>> would want to merge them into your tree without waiting for them to >>>> appear in mainline: >>>> >>>> git pull >git://git=2Ekernel=2Eorg/pub/scm/linux/kernel/git/dtor/input=2Egit >>> ib/4=2E17-xen-kbdfront-runtime-config >>>> Thanks=2E >>>> >>> Thank you, >>> I would prefer the fastest path of course >> It will be part of 4=2E19 pull request; the immutable branch is for >Juergen if he does not want to wait till 4=2E19 merge window to get the >changes=2E >Ah, I see=2E Juergen, can we please merge this via Xen tree then which >I assume will be faster? We are in the tail end of 4=2E18 merge window so it should not make it in = 4=2E18 no matter what tree the patches will go through=2E Thanks=2E --=20 Dmitry