linux-kernel - [PATCH 2/3] drivers:staging:ti-st: drop the __KERNEL_

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Sep 2010 16:13:29 -0400
From:	pavan_savoy@...com
To:	gregkh@...e.de, alan@...rguk.ukuu.org.uk
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	Pavan Savoy <pavan_savoy@...com>
Subject: [PATCH 2/3] drivers:staging:ti-st: drop the __KERNEL__

From: Pavan Savoy <pavan_savoy@...com>

ti_wilink_st.h had the line discipline number which the user-space
daemon refers to, to install and un-install the line discipline upon
request from the shared transport driver via rfkill device.

On moving this line discipline number to standard location of tty.h
drop the __KERNEL__ flag in the header, since the header file would
no longer be used by user-space.

Signed-off-by: Pavan Savoy <pavan_savoy@...com>
---
 drivers/staging/ti-st/ti_wilink_st.h |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/ti-st/ti_wilink_st.h b/drivers/staging/ti-st/ti_wilink_st.h
index afb0cc6..2a5acf5 100644
--- a/drivers/staging/ti-st/ti_wilink_st.h
+++ b/drivers/staging/ti-st/ti_wilink_st.h
@@ -25,7 +25,6 @@
 #ifndef TI_WILINK_ST_H
 #define TI_WILINK_ST_H
 
-#ifdef __KERNEL__
 /**
  * enum kim_gpio_state - Few protocols such as FM have ACTIVE LOW
  *	gpio states for their chip/core enable gpios
@@ -400,5 +399,4 @@ struct gps_event_hdr {
 	u16 plen;
 } __attribute__ ((packed));
 
-#endif /* __KERNEL__ */
 #endif /* TI_WILINK_ST_H */
-- 
1.6.5

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