linux-kernel - Re: [PATCH] component: fix build warning on arm64 builds

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] [day] [month] [year] [list]

Date:	Wed, 25 Mar 2015 15:11:52 +0100
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Russell King <rmk+kernel@....linux.org.uk>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] component: fix build warning on arm64 builds

On Fri, Feb 20, 2015 at 08:59:24AM +0000, Russell King wrote:
> Fix:
> drivers/base/component.c: In function 'find_components':
> drivers/base/component.c:97:3: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'size_t' [-Wformat]
> on ARM64 builds.
> 
> Signed-off-by: Russell King <rmk+kernel@....linux.org.uk>
> ---
>  drivers/base/component.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/base/component.c b/drivers/base/component.c
> index a6f2050d17b7..d99b06b341fb 100644
> --- a/drivers/base/component.c
> +++ b/drivers/base/component.c
> @@ -94,7 +94,7 @@ static int find_components(struct master *master)
>  	for (i = 0; i < match->num; i++) {
>  		struct component *c;
>  
> -		dev_dbg(master->dev, "Looking for component %u\n", i);
> +		dev_dbg(master->dev, "Looking for component %zu\n", i);
>  
>  		if (match->compare[i].component)
>  			continue;
> -- 
> 1.8.3.1

Doesn't apply to my tree, is this already upstream?

thanks,

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/