From: Andi Kleen <ak@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org, bcrl@redhat.com
Subject: Re: [PATCH] Re: 2.5.3-pre1 compile error
Date: 16 Jan 2002 12:27:28 +0100 [thread overview]
Message-ID: <p73pu4aa63j.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20020115192048.G17477@redhat.com.suse.lists.linux.kernel> <Pine.LNX.4.33.0201151628440.1140-100000@penguin.transmeta.com.suse.lists.linux.kernel>
In-Reply-To: Linus Torvalds's message of "16 Jan 2002 01:33:44 +0100"
Linus Torvalds <torvalds@transmeta.com> writes:
>
> > +#ifndef __ASM__ATOMIC_H
> > +#include <asm/atomic.h>
> > +#endif
>
> Please do not assume knowdledge of what the different header files use to
> define their re-entrancy.
>
> Just do
>
> #include <asm/atomic.h>
>
> and be done with it.
The first check is done automatically by the gcc preprocessor
anyways (it has a special check for the #ifndef BLA_H #define BLA_H #endif
construct for whole files and doesn't even bother to open them again on a
second include). So it's completely unnecessary.
Someone added some of these useless checks to 2.5.3pre1. Here is a patch
to remove them. Please consider applying.
--- linux-2.5.3pre1/include/linux/file.h-o Wed Jan 16 12:24:09 2002
+++ linux-2.5.3pre1/include/linux/file.h Wed Jan 16 12:25:10 2002
@@ -5,12 +5,8 @@
#ifndef __LINUX_FILE_H
#define __LINUX_FILE_H
-#ifndef _LINUX_POSIX_TYPES_H /* __FD_CLR */
#include <linux/posix_types.h>
-#endif
-#ifndef __LINUX_COMPILER_H /* unlikely */
#include <linux/compiler.h>
-#endif
/*
* The default fd array needs to be at least BITS_PER_LONG,
--- linux-2.5.3pre1/include/linux/init_task.h-o Wed Jan 16 12:24:09 2002
+++ linux-2.5.3pre1/include/linux/init_task.h Wed Jan 16 12:25:27 2002
@@ -1,9 +1,7 @@
#ifndef _LINUX__INIT_TASK_H
#define _LINUX__INIT_TASK_H
-#ifndef __LINUX_FILE_H
#include <linux/file.h>
-#endif
#define INIT_FILES \
{ \
-Andi
next parent reply other threads:[~2002-01-16 11:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020115192048.G17477@redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0201151628440.1140-100000@penguin.transmeta.com.suse.lists.linux.kernel>
2002-01-16 11:27 ` Andi Kleen [this message]
2002-01-16 11:39 ` [PATCH] Re: 2.5.3-pre1 compile error Dave Jones
2002-01-17 7:40 ` Neil Booth
[not found] <fa.oa9ld7v.gk65b0@ifi.uio.no>
[not found] ` <fa.g97h3fv.968725@ifi.uio.no>
2002-01-16 4:59 ` Russ Allbery
[not found] <20020115194425.J17477@redhat.com>
2002-01-16 0:52 ` Davide Libenzi
2002-01-16 1:16 ` David Weinehall
2002-01-16 1:24 ` Davide Libenzi
2002-01-16 0:05 John Weber
2002-01-16 0:20 ` [PATCH] " Benjamin LaHaise
2002-01-16 0:29 ` Linus Torvalds
2002-01-16 0:38 ` David Weinehall
2002-01-16 0:41 ` Linus Torvalds
2002-01-16 0:55 ` Dave Jones
2002-01-16 2:10 ` dmeyer
2002-01-16 18:32 ` Peter Osterlund
2002-01-16 0:43 ` Benjamin LaHaise
2002-01-16 0:44 ` Linus Torvalds
2002-01-16 0:52 ` Benjamin LaHaise
2002-01-16 1:18 ` David Weinehall
2002-01-17 22:11 ` Christopher Turcksin
2002-01-16 1:24 ` Robert Love
2002-01-16 1:25 ` Benjamin LaHaise
2002-01-16 1:39 ` Robert Love
2002-01-16 0:46 ` Davide Libenzi
2002-01-16 0:43 ` Linus Torvalds
2002-01-16 0:52 ` David S. Miller
2002-01-16 1:06 ` Andre Hedrick
2002-01-16 1:17 ` Davide Libenzi
2002-01-16 1:23 ` Davide Libenzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p73pu4aa63j.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.