lkml.org 
[lkml]   [2019]   [Apr]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
Subject[PATCH] uapi:libc-compat.h: Correct the comment about the value of __UAPI_DEF_FOO
In reality, when the userspace libc header has been included first, we need
to set the value of guard macros to 0, and set the value of guard macros to
1 when uapi header comes first.

Signed-off-by: Wang YanQing <udknight@gmail.com>
---
include/uapi/linux/libc-compat.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/uapi/linux/libc-compat.h b/include/uapi/linux/libc-compat.h
index 8254c93..ba10eede 100644
--- a/include/uapi/linux/libc-compat.h
+++ b/include/uapi/linux/libc-compat.h
@@ -25,8 +25,8 @@
* userspace libc header has been included first.
*
* (c) If the userspace libc header has been included first define a set of
- * guard macros of the form __UAPI_DEF_FOO and set their values to 1, else
- * set their values to 0.
+ * guard macros of the form __UAPI_DEF_FOO and set their values to 0, else
+ * set their values to 1.
*
* (d) Back in the UAPI header with the conflicting definitions, guard the
* definitions with:
--
1.8.5.6.2.g3d8a54e.dirty
\
 
 \ /
  Last update: 2019-04-18 20:24    [W:0.046 / U:13.692 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site