Message-ID: <1a56ea3904091807437ce86616@mail.gmail.com>
Date: Sat, 18 Sep 2004 15:43:08 +0100
From: DaMouse <damouse@gmail.com>
Reply-To: DaMouse <damouse@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: FASTCALL fixing?
In-Reply-To: <200409172223.i8HMNgNu004437@harpo.it.uu.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <200409172223.i8HMNgNu004437@harpo.it.uu.se>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 920
Lines: 24

On Sat, 18 Sep 2004 00:23:42 +0200 (MEST), Mikael Pettersson
<mikpe@csd.uu.se> wrote:
> On Fri, 17 Sep 2004 18:38:46 +0100, DaMouse <damouse@gmail.com> wrote:
> >       I get errors about the fastcall and type conflicts in 2.4.27
> >(yeah its old.. i know :) ) I was wondering what the politically
> >correct way of fixing these are? adding fastcall type to
> >kernel/sched.c or removing FASTCALL() around it in sched.h?
> 
> gcc-3.4? Known issue. Fixed in 2.4.28-pre ages ago,
> as the LKML archives should have told you.
> 

Yeah, sorry i didn't think to look in 2.4.28-pre, thanks :)

-DaMouse


-- 
I know I broke SOMETHING but its there fault for not fixing it before me
-
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/