From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932192AbWAQQz2 (ORCPT ); Tue, 17 Jan 2006 11:55:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932197AbWAQQz2 (ORCPT ); Tue, 17 Jan 2006 11:55:28 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:4739 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S932192AbWAQQz1 (ORCPT ); Tue, 17 Jan 2006 11:55:27 -0500 Date: Tue, 17 Jan 2006 17:55:20 +0100 (MET) From: Jan Engelhardt To: Keith Owens cc: linux-kernel@vger.kernel.org Subject: Re: Suggested janitor task - remove __init/__exit from function prototypes In-Reply-To: <31582.1137291095@ocs3.ocs.com.au> Message-ID: References: <31582.1137291095@ocs3.ocs.com.au> 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 >Some function prototypes (in both .h and .c files) specify attributes >like __init and __exit in the prototype. gcc (at least at 3.3.3) uses >the last such attribute that is actually specified, without issuing a >warning. How does gcc 2.95 handle it, requiring __init in both spots? Jan Engelhardt --