linux-kernel - Re: [PATCH -next] firmware: fix google/gsmi.c build warning

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]

Date:	Wed, 27 Jul 2011 12:49:59 -0700
From:	Mike Waychison <mikew@...gle.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	akpm <akpm@...ux-foundation.org>, linux-next@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -next] firmware: fix google/gsmi.c build warning

On Wed, Jul 27, 2011 at 10:11 AM, Randy Dunlap <rdunlap@...otime.net> wrote:
> From: Randy Dunlap <rdunlap@...otime.net>
>
> Modify function parameter type to match expected type.  Fixes a
> build warning:
>
> drivers/firmware/google/gsmi.c:473: warning: initialization from incompatible pointer type
>
> Signed-off-by: Randy Dunlap <rdunlap@...otime.net>
> Cc: Mike Waychison <mikew@...gle.com>
> ---
>  drivers/firmware/google/gsmi.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20110727.orig/drivers/firmware/google/gsmi.c
> +++ linux-next-20110727/drivers/firmware/google/gsmi.c
> @@ -420,7 +420,7 @@ static efi_status_t gsmi_get_next_variab
>
>  static efi_status_t gsmi_set_variable(efi_char16_t *name,
>                                      efi_guid_t *vendor,
> -                                     unsigned long attr,
> +                                     u32 attr,
>                                      unsigned long data_size,
>                                      void *data)
>  {
>

Looks good.
--
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/