linux-kernel - Re: [PATCH]drivers:staging:hv:hv_mouse.c Fix build error in hv

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110407162243.GA31002@suse.de>
Date:	Thu, 7 Apr 2011 09:22:43 -0700
From:	Greg KH <gregkh@...e.de>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH]drivers:staging:hv:hv_mouse.c Fix build error in hv_mouse.

On Thu, Apr 07, 2011 at 07:36:36AM -0700, Justin P. Mattock wrote:
> The patch below fixes a build error..
> 
>   LD [M]  drivers/staging/hv/hv_utils.o
>   CC [M]  drivers/staging/hv/hv_mouse.o
> drivers/staging/hv/hv_mouse.c: In function ‘ReleaseInputDevice’:
> drivers/staging/hv/hv_mouse.c:293:3: error: implicit declaration of function ‘udelay’ [-Werror=implicit-function-declaration]
> drivers/staging/hv/hv_mouse.c: In function ‘MousevscOnReceiveInputReport’:
> drivers/staging/hv/hv_mouse.c:418:27: warning: variable ‘inputDriver’ set but not used [-Wunused-but-set-variable]
> drivers/staging/hv/hv_mouse.c: In function ‘MousevscOnDeviceAdd’:
> drivers/staging/hv/hv_mouse.c:663:27: warning: variable ‘inputDriver’ set but not used [-Wunused-but-set-variable]
> cc1: some warnings being treated as errors
> 
> Signed-off-by: Justin P. Mattock <justinmattock@...il.com>
> 
> ---
>  drivers/staging/hv/hv_mouse.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)

Thanks, but this is already in the linux-next tree and will go to Linus
in a few hours.

greg k-h
--
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/