linux-kernel - [PATCH] Staging:ft1000_debug.c:Renaming __FUNCTION_

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]

Date:	Thu, 03 Apr 2014 17:21:22 +0100
From:	paulmcquad <paulmcquad@...il.com>
To:	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
	viro@...iv.linux.org.uk, gregkh@...uxfoundation.org
Subject: [PATCH] Staging:ft1000_debug.c:Renaming __FUNCTION__

>From f548b09a0fc387b94fee3372c0f7c4de1f281f80 Mon Sep 17 00:00:00 2001
From: Paul McQuade <paulmcquad@...il.com>
Date: Thu, 3 Apr 2014 17:12:20 +0100
Subject: [PATCH] Staging:ft1000_debug.c:Renaming __FUNCTION__

__Function__ gets renamed with __func__

Signed-off-by: Paul McQuade <paulmcquad@...il.com>
---
 drivers/staging/ft1000/ft1000-usb/ft1000_debug.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/ft1000/ft1000-usb/ft1000_debug.c b/drivers/staging/ft1000/ft1000-usb/ft1000_debug.c
index ffdc7f5..dc7647f 100644
--- a/drivers/staging/ft1000/ft1000-usb/ft1000_debug.c
+++ b/drivers/staging/ft1000/ft1000-usb/ft1000_debug.c
@@ -785,7 +785,7 @@ static int ft1000_release(struct inode *inode, struct file *file)
 
     /* initialize application information */
     ft1000dev->appcnt--;
-    DEBUG("ft1000_chdev:%s:appcnt = %d\n", __FUNCTION__, ft1000dev->appcnt);
+    DEBUG("ft1000_chdev:%s:appcnt = %d\n", __func__, ft1000dev->appcnt);
     ft1000dev->app_info[i].fileobject = NULL;
 
     return 0;
-- 
1.8.3.2

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