linux-kernel - [PATCH v3 trivial 6/7] DRM: comment: `gdm_proc_lists' -> `drm_info

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

Message-ID: <027c085f41de46a185246b334f311ea7-mfwitten@gmail.com>
Date:	Tue, 20 Aug 2013 16:05:24 -0000
From:	Michael Witten <mfwitten@...il.com>
To:	Jiri Kosina <trivial@...nel.org>
Cc:	Rob Landley <rob@...dley.net>,
	Randy Dunlap <rdunlap@...radead.org>,
	David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org
Subject: [PATCH v3 trivial 6/7] DRM: comment: `gdm_proc_lists' -> `drm_info_lists'

Date: Thu, 15 Sep 2011 14:43:00 +0000

I assume `gdm_proc_lists' is a vestigial spelling.

Signed-off-by: Michael Witten <mfwitten@...il.com>
---
 drivers/gpu/drm/drm_proc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/drm_proc.c b/drivers/gpu/drm/drm_proc.c
index d7f2324..dfc6f1f 100644
--- a/drivers/gpu/drm/drm_proc.c
+++ b/drivers/gpu/drm/drm_proc.c
@@ -87,7 +87,7 @@ static const struct file_operations drm_proc_fops = {
  * \return Zero on success, non-zero on failure
  *
  * Create a given set of proc files represented by an array of
- * gdm_proc_lists in the given root directory.
+ * drm_info_lists in the given root directory.
  */
 static int drm_proc_create_files(const struct drm_info_list *files, int count,
 			  struct proc_dir_entry *root, struct drm_minor *minor)
-- 
1.7.11.2.252.gc4a64c8

--
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/