[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY2PR0301MB07116F48FBCAC922CD8A33E3A0340@BY2PR0301MB0711.namprd03.prod.outlook.com>
Date: Sun, 25 Jan 2015 18:07:53 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Nicholas Mc Guire <der.herr@...r.at>
CC: Haiyang Zhang <haiyangz@...rosoft.com>,
Jiri Kosina <jkosina@...e.cz>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 3/3 v2] hyperv: hid-hyperv.c: match
wait_for_completion_timeout return type
> -----Original Message-----
> From: Nicholas Mc Guire [mailto:der.herr@...r.at]
> Sent: Sunday, January 25, 2015 6:48 AM
> To: KY Srinivasan
> Cc: Haiyang Zhang; Jiri Kosina; devel@...uxdriverproject.org; linux-
> kernel@...r.kernel.org; Nicholas Mc Guire
> Subject: [PATCH 3/3 v2] hyperv: hid-hyperv.c: match
> wait_for_completion_timeout return type
>
> Signed-off-by: Nicholas Mc Guire <der.herr@...r.at>
Thank you.
Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> ---
>
> v2: fixed subject line
>
> The return type of wait_for_completion_timeout is unsigned long not int.
> This patch fixes up the declarations only.
>
> Patch was compile tested only for x86_64_defconfig + CONFIG_X86_VSMP=y
> CONFIG_HYPERV=m, CONFIG_HID_HYPERV_MOUSE=m
>
> Patch is against 3.19.0-rc5 -next-20150123
>
> drivers/hid/hid-hyperv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hid/hid-hyperv.c b/drivers/hid/hid-hyperv.c index
> 31fad64..6039f07 100644
> --- a/drivers/hid/hid-hyperv.c
> +++ b/drivers/hid/hid-hyperv.c
> @@ -381,7 +381,7 @@ static void mousevsc_on_channel_callback(void
> *context) static int mousevsc_connect_to_vsp(struct hv_device *device) {
> int ret = 0;
> - int t;
> + unsigned long t;
> struct mousevsc_dev *input_dev = hv_get_drvdata(device);
> struct mousevsc_prt_msg *request;
> struct mousevsc_prt_msg *response;
> --
> 1.7.10.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists