Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 19 Apr 2019 02:08:40 +0800
From:   Wang YanQing <udknight@gmail.com>
To:     davem@davemloft.net
Cc:     netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] uapi:libc-compat.h: Correct the comment about the value of
 __UAPI_DEF_FOO
Message-ID: <20190418180840.GB4863@udknight>
Mail-Followup-To: Wang YanQing <udknight@gmail.com>, davem@davemloft.net,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.7.1 (2016-10-04)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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