The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	Manohar Vanga <manohar.vanga@cern.ch>
Subject: Re: [PATCH] vme: vme_ca91cx42.c: local functions should not be exposed globally
Date: Thu, 03 May 2012 16:36:49 +0100	[thread overview]
Message-ID: <4FA2A611.7040106@ge.com> (raw)
In-Reply-To: <201205021712.22325.hartleys@visionengravers.com>

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@visionengravers.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Martyn Welch <martyn.welch@ge.com>

Good catch,

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

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@ge.com                  | VAT:GB 927559189

      reply	other threads:[~2012-05-03 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03  0:12 [PATCH] vme: vme_ca91cx42.c: local functions should not be exposed globally H Hartley Sweeten
2012-05-03 15:36 ` Martyn Welch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FA2A611.7040106@ge.com \
    --to=martyn.welch@ge.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hartleys@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manohar.vanga@cern.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox