linux-kernel - [PATCH] blackfin: includecheck fix: mach-bf548, ezkit.c

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

Message-Id: <1253788689.5860.2.camel@ht.satnam>
Date:	Thu, 24 Sep 2009 16:08:09 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	Mike Frysinger <vapier@...too.org>,
	Michael Hennerich <michael.hennerich@...log.com>,
	uclinux-dist-devel@...ckfin.uclinux.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH] blackfin: includecheck fix: mach-bf548, ezkit.c


fix the following 'make includecheck' warning:

  arch/blackfin/mach-bf548/boards/ezkit.c: linux/input.h is included more than once.

Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@...il.com>
Cc: Mike Frysinger <vapier@...too.org>
Cc: Michael Hennerich <michael.hennerich@...log.com>
---
 arch/blackfin/mach-bf548/boards/ezkit.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/arch/blackfin/mach-bf548/boards/ezkit.c b/arch/blackfin/mach-bf548/boards/ezkit.c
index c66f380..383a18c 100644
--- a/arch/blackfin/mach-bf548/boards/ezkit.c
+++ b/arch/blackfin/mach-bf548/boards/ezkit.c
@@ -208,7 +208,6 @@ static struct platform_device bfin_rotary_device = {
 #endif
 
 #if defined(CONFIG_INPUT_ADXL34X) || defined(CONFIG_INPUT_ADXL34X_MODULE)
-#include <linux/input.h>
 #include <linux/spi/adxl34x.h>
 static const struct adxl34x_platform_data adxl34x_info = {
 	.x_axis_offset = 0,
-- 
1.6.0.6


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