dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de,
	xie.baoyou@zte.com.cn, han.fei@zte.com.cn,
	tang.qiang007@zte.com.cn
Subject: Re: [PATCH] drm: armada: mark symbols static where possible
Date: Mon, 26 Sep 2016 16:17:21 +0100	[thread overview]
Message-ID: <20160926151721.GE1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1474788145-3068-1-git-send-email-baoyou.xie@linaro.org>

On Sun, Sep 25, 2016 at 03:22:25PM +0800, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/gpu/drm/armada/armada_gem.c:215:27: warning: no previous prototype for 'armada_gem_alloc_object' [-Wmissing-prototypes]
> drivers/gpu/drm/armada/armada_gem.c:423:1: warning: no previous prototype for 'armada_gem_prime_map_dma_buf' [-Wmissing-prototypes]
> 
> In fact, these functions are only used in the file in which they are
> declared and don't need a declaration, but can be made static.
> So this patch marks these functions with 'static'.
> 
> Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>

Thanks.  You can have an:

Acked-by: Russell King <rmk+kernel@armlinux.org.uk>

with one change to this patch:

> ---
>  drivers/gpu/drm/armada/armada_gem.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/armada/armada_gem.c b/drivers/gpu/drm/armada/armada_gem.c
> index cb8f034..1beef28 100644
> --- a/drivers/gpu/drm/armada/armada_gem.c
> +++ b/drivers/gpu/drm/armada/armada_gem.c
> @@ -212,7 +212,8 @@ armada_gem_alloc_private_object(struct drm_device *dev, size_t size)
>  	return obj;
>  }
>  
> -struct armada_gem_object *armada_gem_alloc_object(struct drm_device *dev,
> +static struct
> +armada_gem_object *armada_gem_alloc_object(struct drm_device *dev,
>  	size_t size)

Please make this:

static struct armada_gem_object *
armada_gem_alloc_object(struct drm_device *dev, size_t size)

instead - if we're going to break it across lines, there's no need to
break it across three, and always keep the return type on one line,
like the other instance you've modified below.

Thanks.

>  {
>  	struct armada_gem_object *obj;
> @@ -419,7 +420,7 @@ int armada_gem_pwrite_ioctl(struct drm_device *dev, void *data,
>  }
>  
>  /* Prime support */
> -struct sg_table *
> +static struct sg_table *
>  armada_gem_prime_map_dma_buf(struct dma_buf_attachment *attach,
>  	enum dma_data_direction dir)
>  {
> -- 
> 2.7.4
> 

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

      reply	other threads:[~2016-09-26 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-25  7:22 [PATCH] drm: armada: mark symbols static where possible Baoyou Xie
2016-09-26 15:17 ` Russell King - ARM Linux [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=20160926151721.GE1041@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=baoyou.xie@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=han.fei@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tang.qiang007@zte.com.cn \
    --cc=xie.baoyou@zte.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).