Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269549AbUIROnR (ORCPT ); Sat, 18 Sep 2004 10:43:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269533AbUIROnQ (ORCPT ); Sat, 18 Sep 2004 10:43:16 -0400 Received: from rproxy.gmail.com ([64.233.170.201]:46985 "EHLO mproxy.gmail.com") by vger.kernel.org with ESMTP id S269549AbUIROnJ (ORCPT ); Sat, 18 Sep 2004 10:43:09 -0400 Message-ID: <1a56ea3904091807437ce86616@mail.gmail.com> Date: Sat, 18 Sep 2004 15:43:08 +0100 From: DaMouse Reply-To: DaMouse To: LKML 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 X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 920 Lines: 24 On Sat, 18 Sep 2004 00:23:42 +0200 (MEST), Mikael Pettersson wrote: > On Fri, 17 Sep 2004 18:38:46 +0100, DaMouse 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/