public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc3-mm2: error: `u64' used prior to declaration
Date: Mon, 4 Oct 2004 17:35:16 +0200	[thread overview]
Message-ID: <20041004153515.GB12736@stusta.de> (raw)
In-Reply-To: <416160FE.2090107@eyal.emu.id.au>

On Tue, Oct 05, 2004 at 12:41:02AM +1000, Eyal Lebedinsky wrote:

>   CC [M]  drivers/media/dvb/bt8xx/dvb-bt8xx.o
> In file included from drivers/media/dvb/bt8xx/dvb-bt8xx.c:22:
> include/asm/bitops.h:543: error: parse error before "rol64"
>...

The first error is the most interesting one.

> include/asm/types.h: At top level:
> include/asm/types.h:50: error: `u64' used prior to declaration
> make[4]: *** [drivers/media/dvb/bt8xx/dvb-bt8xx.o] Error 1
>...
> 
> I just added
> 	#include <asm/types.h>
> to the top of
> 	include/asm/bitops.h
> and the build finished
>...

The real problem seem to be files including asm/bitops.h instead of 
linux/bitops.h .

@Andrew:
Would you accept a patch that changes all #include <asm/bitops.h> to
#include <linux/bitops.h> ?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-10-04 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 14:41 2.6.9-rc3-mm2: error: `u64' used prior to declaration Eyal Lebedinsky
2004-10-04 15:35 ` Adrian Bunk [this message]
2004-10-04 19:59   ` Andrew Morton
2004-10-04 20:20     ` Adrian Bunk

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=20041004153515.GB12736@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=eyal@eyal.emu.id.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox