Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 14 Aug 2002 22:27:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 14 Aug 2002 22:27:05 -0400 Received: from chaos.physics.uiowa.edu ([128.255.34.189]:56771 "EHLO chaos.physics.uiowa.edu") by vger.kernel.org with ESMTP id ; Wed, 14 Aug 2002 22:27:05 -0400 Date: Wed, 14 Aug 2002 21:30:47 -0500 (CDT) From: Kai Germaschewski X-X-Sender: kai@chaos.physics.uiowa.edu To: Alan Cox cc: Eyal Lebedinsky , Subject: Re: Linux 2.4.20-pre2-ac1 In-Reply-To: <200208150114.g7F1EcY25108@devserv.devel.redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 851 Lines: 22 On Wed, 14 Aug 2002, Alan Cox wrote: > > - drivers/isdn/hisax/st5481.h > > Usage of '...' in macro, not always compatible with prevailing > > versions of gcc. We all know the story though... I just disabled > > all the special macros for now > > I'll ifdef between the two versions again. I'm not using the old gcc on > any boxes nowdays so I don't catch them There surely has to be a way to get that working on all compilers? I seem to remember that adding a space after __FUNCTION__ was necessary in some cases (before the ','). Alas I don't have anything newer than 2.96 for testing here. --Kai - 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/