Linux Input/HID development
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: olaf@aepfle.de, gregkh@linuxfoundation.org, jasowang@redhat.com,
	linux-kernel@vger.kernel.org, vojtech@suse.cz,
	linux-input@vger.kernel.org, apw@canonical.com,
	devel@linuxdriverproject.org
Subject: Re: [PATCH 1/1] Drivers: input: serio:hyperv-keyoard:  Handle 0xE1 prefix
Date: Sun, 12 Jan 2014 11:14:36 -0800	[thread overview]
Message-ID: <20140112191436.GB13131@core.coreip.homeip.net> (raw)
In-Reply-To: <1389498110-4790-1-git-send-email-kys@microsoft.com>

On Sat, Jan 11, 2014 at 07:41:50PM -0800, K. Y. Srinivasan wrote:
> Handle the 0xE1 prefix.
> 
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>

Applied, thank you.

> ---
>  drivers/input/serio/hyperv-keyboard.c |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/input/serio/hyperv-keyboard.c b/drivers/input/serio/hyperv-keyboard.c
> index 3a83c3c..6132619 100644
> --- a/drivers/input/serio/hyperv-keyboard.c
> +++ b/drivers/input/serio/hyperv-keyboard.c
> @@ -160,7 +160,9 @@ static void hv_kbd_on_receive(struct hv_device *hv_dev,
>  			if (info & IS_E0)
>  				serio_interrupt(kbd_dev->hv_serio,
>  						XTKBD_EMUL0, 0);
> -
> +			if (info & IS_E1)
> +				serio_interrupt(kbd_dev->hv_serio,
> +						XTKBD_EMUL1, 0);
>  			scan_code = __le16_to_cpu(ks_msg->make_code);
>  			if (info & IS_BREAK)
>  				scan_code |= XTKBD_RELEASE;
> -- 
> 1.7.4.1
> 

-- 
Dmitry

      reply	other threads:[~2014-01-12 19:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12  3:41 [PATCH 1/1] Drivers: input: serio:hyperv-keyoard: Handle 0xE1 prefix K. Y. Srinivasan
2014-01-12 19:14 ` Dmitry Torokhov [this message]

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=20140112191436.GB13131@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=vojtech@suse.cz \
    /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