linux-kernel - [PATCH 4/6] microblaze: fix compiler warning by properly inlining flat_set

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]

Date:	Sat,  9 Jun 2012 05:13:29 -0300
From:	Ezequiel Garcia <elezegarcia@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-arch@...r.kernel.org,
	Ezequiel Garcia <elezegarcia@...il.com>,
	Michal Simek <monstr@...str.eu>,
	<microblaze-uclinux@...e.uq.edu.au>
Subject: [PATCH 4/6] microblaze: fix compiler warning by properly inlining flat_set_persistent()

This patch removes the following warning:
fs/binfmt_flat.c:752: warning: unused variable ‘persistent’
There is neither change in functionality, nor extra code generated.

Cc: Michal Simek <monstr@...str.eu>
Cc: <microblaze-uclinux@...e.uq.edu.au>
Signed-off-by: Ezequiel Garcia <elezegarcia@...il.com>
---
 arch/microblaze/include/asm/flat.h |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/arch/microblaze/include/asm/flat.h b/arch/microblaze/include/asm/flat.h
index 6847c15..40602c8 100644
--- a/arch/microblaze/include/asm/flat.h
+++ b/arch/microblaze/include/asm/flat.h
@@ -16,7 +16,12 @@
 #define	flat_argvp_envp_on_stack()	0
 #define	flat_old_ram_flag(flags)	(flags)
 #define	flat_reloc_valid(reloc, size)	((reloc) <= (size))
-#define	flat_set_persistent(relval, p)		0
+
+static inline int flat_set_persistent(unsigned long relval,
+				      unsigned long *persistent)
+{
+	return 0;
+}
 
 /*
  * Microblaze works a little differently from other arches, because
-- 
1.7.3.4

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