public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [drm:drm-opt-pwr 84/84] drivers/gpu/drm/nouveau/nouveau_drm.c:628:6: sparse: symbol 'nouveau_drm_ioc
Date: Wed, 12 Sep 2012 07:34:12 +0000	[thread overview]
Message-ID: <20120912073412.GC26877@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

Hi Dave,

FYI, there are new sparse warnings show up in

tree:   git://people.freedesktop.org/~airlied/linux.git drm-opt-pwr
head:   75c2c97fd7c783f4f06423a41671f61840e65fa5
commit: 75c2c97fd7c783f4f06423a41671f61840e65fa5 [84/84] nouveau: add runtime PM support (v0.5)

All sparse warnings:

  drivers/gpu/drm/nouveau/nouveau_drm.c:406:1: sparse: symbol 'nouveau_do_suspend' was not declared. Should it be static?
  drivers/gpu/drm/nouveau/nouveau_drm.c:468:1: sparse: symbol 'nouveau_do_resume' was not declared. Should it be static?
+ drivers/gpu/drm/nouveau/nouveau_drm.c:628:6: sparse: symbol 'nouveau_drm_ioctl' was not declared. Should it be static?

vim +628 drivers/gpu/drm/nouveau/nouveau_drm.c

 > 628	long nouveau_drm_ioctl(struct file *filp,
   629			       unsigned int cmd, unsigned long arg)
   630	{
   631		struct drm_file *file_priv = filp->private_data;
   632		struct drm_device *dev;
   633		long ret;
   634		dev = file_priv->minor->dev;
   635		ret = pm_runtime_get(dev->dev);
   636		if (ret < 0)
   637			return ret;
   638	

Please consider folding the attached diff :-)

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation

[-- Attachment #2: make-it-static-75c2c97.diff --]
[-- Type: text/x-diff, Size: 930 bytes --]

diff --git a/drivers/gpu/drm/nouveau/nouveau_drm.c b/drivers/gpu/drm/nouveau/nouveau_drm.c
index a7258d9..1d68173 100644
--- a/drivers/gpu/drm/nouveau/nouveau_drm.c
+++ b/drivers/gpu/drm/nouveau/nouveau_drm.c
@@ -402,7 +402,7 @@ nouveau_drm_remove(struct pci_dev *pdev)
 	nouveau_object_debug();
 }
 
-int
+static int
 nouveau_do_suspend(struct drm_device *dev)
 {
 	struct nouveau_drm *drm = nouveau_drm(dev);
@@ -464,7 +464,7 @@ int nouveau_pmops_suspend(struct device *dev)
 	return 0;
 }
 
-int
+static int
 nouveau_do_resume(struct drm_device *dev)
 {
 	struct nouveau_drm *drm = nouveau_drm(dev);
@@ -625,7 +625,7 @@ nouveau_ioctls[] = {
 	DRM_IOCTL_DEF_DRV(NOUVEAU_GEM_INFO, nouveau_gem_ioctl_info, DRM_UNLOCKED|DRM_AUTH),
 };
 
-long nouveau_drm_ioctl(struct file *filp,
+static long nouveau_drm_ioctl(struct file *filp,
 		       unsigned int cmd, unsigned long arg)
 {
 	struct drm_file *file_priv = filp->private_data;

                 reply	other threads:[~2012-09-12  7:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120912073412.GC26877@localhost \
    --to=fengguang.wu@intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    /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