public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: airlied@linux.ie, ykk@rock-chips.com, inki.dae@samsung.com,
	seanpaul@chromium.org, gustavo.padovan@collabora.co.uk,
	daniel.vetter@ffwll.ch, ville.syrjala@linux.intel.com,
	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: bridge: analogix/dp: mark symbols static where possible
Date: Sun, 25 Sep 2016 23:02:18 +0200	[thread overview]
Message-ID: <20160925210218.GT20761@phenom.ffwll.local> (raw)
In-Reply-To: <1474788764-6069-1-git-send-email-baoyou.xie@linaro.org>

On Sun, Sep 25, 2016 at 03:32:44PM +0800, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/gpu/drm/bridge/analogix/analogix_dp_core.c:1053:5: warning: no previous prototype for 'analogix_dp_get_modes' [-Wmissing-prototypes]
> drivers/gpu/drm/bridge/analogix/analogix_dp_core.c:1097:1: warning: no previous prototype for 'analogix_dp_detect' [-Wmissing-prototypes]
> 
> In fact, both 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 both functions with 'static'.
> 
> Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>

This and your drm/bochs patch applied to drm-misc, thanks.
-Daniel

> ---
>  drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
> index efac8ab..e6f7290 100644
> --- a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
> +++ b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
> @@ -1050,7 +1050,7 @@ out:
>  	return ret;
>  }
>  
> -int analogix_dp_get_modes(struct drm_connector *connector)
> +static int analogix_dp_get_modes(struct drm_connector *connector)
>  {
>  	struct analogix_dp_device *dp = to_dp(connector);
>  	struct edid *edid = (struct edid *)dp->edid;
> @@ -1093,7 +1093,7 @@ static const struct drm_connector_helper_funcs analogix_dp_connector_helper_func
>  	.best_encoder = analogix_dp_best_encoder,
>  };
>  
> -enum drm_connector_status
> +static enum drm_connector_status
>  analogix_dp_detect(struct drm_connector *connector, bool force)
>  {
>  	struct analogix_dp_device *dp = to_dp(connector);
> -- 
> 2.7.4
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2016-09-25 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-25  7:32 [PATCH] drm: bridge: analogix/dp: mark symbols static where possible Baoyou Xie
2016-09-25 21:02 ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-18 13:54 Baoyou Xie

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=20160925210218.GT20761@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=baoyou.xie@linaro.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=han.fei@zte.com.cn \
    --cc=inki.dae@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanpaul@chromium.org \
    --cc=tang.qiang007@zte.com.cn \
    --cc=ville.syrjala@linux.intel.com \
    --cc=xie.baoyou@zte.com.cn \
    --cc=ykk@rock-chips.com \
    /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