Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756923AbXFMHtR (ORCPT ); Wed, 13 Jun 2007 03:49:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756081AbXFMHtH (ORCPT ); Wed, 13 Jun 2007 03:49:07 -0400 Received: from charybdis-ext.suse.de ([195.135.221.2]:54936 "EHLO emea5-mh.id5.novell.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756059AbXFMHtF convert rfc822-to-8bit (ORCPT ); Wed, 13 Jun 2007 03:49:05 -0400 Message-Id: <466FBDC1.76E4.0078.0@novell.com> X-Mailer: Novell GroupWise Internet Agent 7.0.2 HP Date: Wed, 13 Jun 2007 09:49:53 +0200 From: "Jan Beulich" To: "Satyam Sharma" Cc: "Venkatesh Pallipadi" , "Sam Ravnborg" , "Andi Kleen" , , Subject: Re: [PATCH] x86: fix improper .init-type section references References: <466E6BDF.76E4.0078.0@novell.com> <466EB12B.76E4.0078.0@novell.com> <466EC08A.76E4.0078.0@novell.com> <20070612180002.GC15329@uranus.ravnborg.org> <20070613043526.GA20088@uranus.ravnborg.org> <466FB20D.76E4.0078.0@novell.com> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 791 Lines: 18 >But then why not simply lose the __exit (and .exit.*) altogether? Because >__exit becomes redundant in the suggested changed semantics -- just mark >all the cleanup code as __init too (when it's built-in, the only >callsite for the >cleanup code would be from the startup code in .init.*, and when modular, >__init and __exit lose all relevance anyway). Because of the non-builtin case (__init still has significance in the modular case, it's only __exit that doesn't). For the builtin case, __init could certainly be identical to __exit. Jan - 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/