Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269101AbUIQWeN (ORCPT ); Fri, 17 Sep 2004 18:34:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269231AbUIQWeG (ORCPT ); Fri, 17 Sep 2004 18:34:06 -0400 Received: from aun.it.uu.se ([130.238.12.36]:12221 "EHLO aun.it.uu.se") by vger.kernel.org with ESMTP id S269101AbUIQWbl (ORCPT ); Fri, 17 Sep 2004 18:31:41 -0400 Date: Sat, 18 Sep 2004 00:23:42 +0200 (MEST) Message-Id: <200409172223.i8HMNgNu004437@harpo.it.uu.se> From: Mikael Pettersson To: damouse@gmail.com, linux-kernel@vger.kernel.org Subject: Re: FASTCALL fixing? Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 665 Lines: 13 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. - 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/