Re: [PATCH] vme: vme_ca91cx42.c: local functions should not be exposedglobally

From: Martyn Welch
Date: Thu May 03 2012 - 11:36:58 EST


On 03/05/12 01:12, H Hartley Sweeten wrote:
> Functions not referenced outside of a source file should be marked
> static to prevent them from being exposed globally.
>
> Quiets the sparse warnings:
>
> warning: symbol 'ca91cx42_alloc_consistent' was not declared. Should it be static?
> warning: symbol 'ca91cx42_free_consistent' was not declared. Should it be static?
>
> Signed-off-by: H Hartley Sweeten <hsweeten@xxxxxxxxxxxxxxxxxxx>
> Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> Cc: Martyn Welch <martyn.welch@xxxxxx>

Good catch,

Acked-by: Martyn Welch <martyn.welch@xxxxxx>

Martyn

>
> ---
>
> diff --git a/drivers/vme/bridges/vme_ca91cx42.c b/drivers/vme/bridges/vme_ca91cx42.c
> index a3c0f84..e0df92e 100644
> --- a/drivers/vme/bridges/vme_ca91cx42.c
> +++ b/drivers/vme/bridges/vme_ca91cx42.c
> @@ -1501,7 +1501,7 @@ static int ca91cx42_slot_get(struct vme_bridge *ca91cx42_bridge)
>
> }
>
> -void *ca91cx42_alloc_consistent(struct device *parent, size_t size,
> +static void *ca91cx42_alloc_consistent(struct device *parent, size_t size,
> dma_addr_t *dma)
> {
> struct pci_dev *pdev;
> @@ -1512,8 +1512,8 @@ void *ca91cx42_alloc_consistent(struct device *parent, size_t size,
> return pci_alloc_consistent(pdev, size, dma);
> }
>
> -void ca91cx42_free_consistent(struct device *parent, size_t size, void *vaddr,
> - dma_addr_t dma)
> +static void ca91cx42_free_consistent(struct device *parent, size_t size,
> + void *vaddr, dma_addr_t dma)
> {
> struct pci_dev *pdev;
>


--
Martyn Welch (Lead Software Engineer) | Registered in England and Wales
GE Intelligent Platforms | (3828642) at 100 Barbirolli Square
T +44(0)1327322748 | Manchester, M2 3AB
E martyn.welch@xxxxxx | VAT:GB 927559189
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/