Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755698AbYCWGcF (ORCPT ); Sun, 23 Mar 2008 02:32:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752527AbYCWGbz (ORCPT ); Sun, 23 Mar 2008 02:31:55 -0400 Received: from astoria.ccjclearline.com ([64.235.106.9]:38605 "EHLO astoria.ccjclearline.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752523AbYCWGby (ORCPT ); Sun, 23 Mar 2008 02:31:54 -0400 Date: Sun, 23 Mar 2008 02:31:51 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost.localdomain To: Linux Kernel Mailing List Subject: why so many unexported headers checking __KERNEL__? Message-ID: User-Agent: Alpine 1.00 (LFD 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - astoria.ccjclearline.com X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crashcourse.ca X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 868 Lines: 22 as an unintended side effect of checking for proper exporting to user space and unifdef'ing, i noticed that there are literally hundreds of kernel header files that check the value of __KERNEL__ in some way, but are never exported to user space. what's the point of that? thanks. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture. http://crashcourse.ca Waterloo, Ontario, CANADA ======================================================================== -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/