From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935379AbWLANDe (ORCPT ); Fri, 1 Dec 2006 08:03:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S936486AbWLANDe (ORCPT ); Fri, 1 Dec 2006 08:03:34 -0500 Received: from nic.NetDirect.CA ([216.16.235.2]:52884 "EHLO rubicon.netdirect.ca") by vger.kernel.org with ESMTP id S935379AbWLANDa (ORCPT ); Fri, 1 Dec 2006 08:03:30 -0500 X-Originating-Ip: 74.109.98.100 Date: Fri, 1 Dec 2006 08:00:11 -0500 (EST) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost.localdomain To: Linux kernel mailing list Subject: how many "KERNEL" macro variations do we really need? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Net-Direct-Inc-MailScanner-Information: Please contact the ISP for more information X-Net-Direct-Inc-MailScanner: Found to be clean X-Net-Direct-Inc-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-16.8, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -15.00, UPPERCASE_25_50 0.00) X-Net-Direct-Inc-MailScanner-From: rpjday@mindspring.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org i'm sure there's a simpler way to write this: include/linux/soundcard.h: #if (!defined(__KERNEL__) && !defined(KERNEL) && !defined(INKERNEL) && !defined(_KERNEL)) || defined(USE_SEQ_MACROS) __KERNEL__ versus KERNEL versus INKERNEL versus _KERNEL? surely, those can't *all* be necessary. or can they? rday