linux-kernel - Re: [PATCH] gpu: ion: fix sparse non static symbol warnings

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]

Message-ID: <20140211202547.GA11684@kroah.com>
Date:	Tue, 11 Feb 2014 12:25:47 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Daeseok Youn <daeseok.youn@...il.com>
Cc:	john.stultz@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gpu: ion: fix sparse non static symbol warnings

On Mon, Feb 10, 2014 at 09:32:22AM +0900, Daeseok Youn wrote:
> >From 08b77be03927d450810c07d3a4440dc8c32fe766 Mon Sep 17 00:00:00 2001
> From: Daeseok Youn <daeseok.youn@...il.com>
> Date: Mon, 10 Feb 2014 09:02:26 +0900
> Subject: [PATCH] gpu: ion: fix sparse non static symbol warnings
> 
> Fixes the following sparse warnings:
> 
> drivers/staging/android/ion/ion_dummy_driver.c:26:19:
>  warning: symbol 'idev' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:27:17:
>  warning: symbol 'heaps' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:29:6:
>  warning: symbol 'carveout_ptr' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:30:6:
>  warning: symbol 'chunk_ptr' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:32:26:
>  warning: symbol 'dummy_heaps' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:59:26:
>  warning: symbol 'dummy_ion_pdata' was not declared. Should it be static?
> 
> Signed-off-by: Daeseok Youn <daeseok.youn@...il.com>

This patch has already been made in my tree, please always work against
linux-next to prevent duplication of work.

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/