From: Martin Dalecki <dalecki@evision-ventures.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.5 patch] hdreg.h must include types.h
Date: Thu, 04 Apr 2002 11:18:01 +0200 [thread overview]
Message-ID: <3CAC1A49.9040509@evision-ventures.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0204040938300.7845-100000@mimas.fachschaften.tu-muenchen.de>
Adrian Bunk wrote:
> Hi,
>
> while compiling 2.5.7-dj3 I got the following compile error:
>
> <-- snip -->
>
> ...
> gcc -D__KERNEL__ -I/home/bunk/linux/kernel-2.5/linux-2.5.7/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
> -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -DKBUILD_BASENAME=ide_pnp
> -c -o ide-pnp.o ide-pnp.c
> In file included from /home/bunk/linux/kernel-2.5/linux-2.5.7/include/linux/ide.h:10,
> from ide-pnp.c:19:
> /home/bunk/linux/kernel-2.5/linux-2.5.7/include/linux/hdreg.h:71: parse
> error before `u8'
>
> <-- snip -->
>
> The problem is that in 2.5.8-pre1 hdreg.h uses u8 but it doesn't include
> types.h. I didn't tried it but since the code is the same I expect the
> same problem in 2.5.8-pre1, too.
>
> The fix is simple:
>
> --- include/linux/hdreg.h.old Thu Apr 4 09:33:48 2002
> +++ include/linux/hdreg.h Thu Apr 4 09:34:44 2002
> @@ -1,6 +1,8 @@
> #ifndef _LINUX_HDREG_H
> #define _LINUX_HDREG_H
>
> +#include <linux/types.h>
> +
> /*
> * This file contains some defines for the AT-hd-controller.
> * Various sources.
>
> cu
> Adrian
>
The proper fix is to add linux/types.h in ide-pnp.c in front
of linux/hdreg.h inclusion. Nested includes are *nasty*.
next prev parent reply other threads:[~2002-04-04 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 7:42 [2.5 patch] hdreg.h must include types.h Adrian Bunk
2002-04-04 9:18 ` Martin Dalecki [this message]
2002-04-04 14:50 ` Adrian Bunk
2002-04-09 7:37 ` Frank Schaefer
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=3CAC1A49.9040509@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
/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.