linux-kernel - Re: [PATCH drm-intel] drm/i915: gen6_gmch

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>] [day] [month] [year] [list]

Message-ID: <20130131083841.GC5885@phenom.ffwll.local>
Date:	Thu, 31 Jan 2013 09:38:41 +0100
From:	Daniel Vetter <daniel@...ll.ch>
To:	Changlong Xie <changlongx.xie@...el.com>
Cc:	Daniel Vetter <daniel.vetter@...ll.ch>,
	Ben Widawsky <ben@...dawsk.net>, linux-kernel@...r.kernel.org,
	Intel Graphics Development <intel-gfx@...ts.freedesktop.org>
Subject: Re: [PATCH drm-intel] drm/i915: gen6_gmch_remove can be static

On Thu, Jan 31, 2013 at 11:32:50AM +0800, Changlong Xie wrote:
> Signed_off_by: Changlong Xie <changlongx.xie@...el.com>
> Reported-by: Fengguang Wu <fengguang.wu@...el.com>

Queued for -next, thanks for the patch. Note that checkpatch complained
about the _ instead of - in your sob line, fixed up while applying.
-Daniel

> ---
>  i915_gem_gtt.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
> index 87249e8..748015b 100644
> --- a/drivers/gpu/drm/i915/i915_gem_gtt.c
> +++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
> @@ -773,7 +773,7 @@ static int gen6_gmch_probe(struct drm_device *dev,
>  	return ret;
>  }
>  
> -void gen6_gmch_remove(struct drm_device *dev)
> +static void gen6_gmch_remove(struct drm_device *dev)
>  {
>  	struct drm_i915_private *dev_priv = dev->dev_private;
>  	iounmap(dev_priv->gtt.gsm);

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
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/