linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: xen-devel@lists.xenproject.org, dmitry.torokhov@gmail.com,
	jandryuk@gmail.com,
	Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH v4 1/2] xen/kbdif: Add string constants for raw pointer
Date: Fri, 11 May 2018 09:37:57 -0400	[thread overview]
Message-ID: <20180511133757.GG19972@char.us.oracle.com> (raw)
In-Reply-To: <20180502144919.16780-1-andr2000@gmail.com>

On Wed, May 02, 2018 at 05:49:18PM +0300, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
> 
> Add missing string constants for {feature|request}-raw-pointer
> to align with the rest of the interface file.
> 
> Fixes 7868654ff7fe ("kbdif: Define "feature-raw-pointer" and "request-raw-pointer")
> 
> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>


Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

Thank you!
> ---
>  xen/include/public/io/kbdif.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/xen/include/public/io/kbdif.h b/xen/include/public/io/kbdif.h
> index 3ce54e9a44c1..daf4bc2063c9 100644
> --- a/xen/include/public/io/kbdif.h
> +++ b/xen/include/public/io/kbdif.h
> @@ -178,8 +178,10 @@
>  #define XENKBD_DRIVER_NAME             "vkbd"
>  
>  #define XENKBD_FIELD_FEAT_ABS_POINTER  "feature-abs-pointer"
> +#define XENKBD_FIELD_FEAT_RAW_POINTER  "feature-raw-pointer"
>  #define XENKBD_FIELD_FEAT_MTOUCH       "feature-multi-touch"
>  #define XENKBD_FIELD_REQ_ABS_POINTER   "request-abs-pointer"
> +#define XENKBD_FIELD_REQ_RAW_POINTER   "request-raw-pointer"
>  #define XENKBD_FIELD_REQ_MTOUCH        "request-multi-touch"
>  #define XENKBD_FIELD_RING_GREF         "page-gref"
>  #define XENKBD_FIELD_EVT_CHANNEL       "event-channel"
> -- 
> 2.17.0
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2018-05-11 13:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 14:49 [PATCH v4 1/2] xen/kbdif: Add string constants for raw pointer Oleksandr Andrushchenko
2018-05-02 14:49 ` [PATCH v4 2/2] xen/kbdif: Add features to disable keyboard and pointer Oleksandr Andrushchenko
2018-05-17  5:45   ` Oleksandr Andrushchenko
2018-05-17  5:50     ` Juergen Gross
2018-05-17  5:51       ` Oleksandr Andrushchenko
2018-05-17 14:09         ` Konrad Rzeszutek Wilk
2018-05-17 18:41           ` Oleksandr Andrushchenko
2018-05-08  5:41 ` [PATCH v4 1/2] xen/kbdif: Add string constants for raw pointer Oleksandr Andrushchenko
2018-05-11 13:37 ` Konrad Rzeszutek Wilk [this message]
2018-05-11 13:38   ` Konrad Rzeszutek Wilk
2018-05-11 15:15     ` Juergen Gross
2018-05-16  4:59       ` Oleksandr Andrushchenko
2018-05-17  4:28         ` Juergen Gross
2018-05-17  5:29           ` Oleksandr Andrushchenko
2018-05-17  5:42             ` Juergen Gross
2018-05-17  5:47               ` Oleksandr Andrushchenko

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=20180511133757.GG19972@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=andr2000@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jandryuk@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=oleksandr_andrushchenko@epam.com \
    --cc=xen-devel@lists.xenproject.org \
    /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).