Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 15 Mar 2002 21:26:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 15 Mar 2002 21:26:11 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:13326 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id ; Fri, 15 Mar 2002 21:26:02 -0500 Message-ID: <3C92AD1F.30909@mandrakesoft.com> Date: Fri, 15 Mar 2002 21:25:35 -0500 From: Jeff Garzik User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020214 X-Accept-Language: en MIME-Version: 1.0 To: Linus Torvalds CC: Anders Gustafsson , arjanv@redhat.com, linux-kernel@vger.kernel.org, mochel@osdl.org Subject: Re: [PATCH] devexit fixes in i82092.c In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds wrote: > >On Sat, 16 Mar 2002, Anders Gustafsson wrote: > >>this patch fixes "undefined reference to `local symbols in discarded >>section .text.exit'" linking error. >> > >Looking more at this, I actually think that the _real_ fix is to call all >drivers exit functions at kernel shutdown, and not discard the exit >section when linking into the tree. > >That, together with the device tree, automatically gives us the >_correct_ shutdown sequence, soemthing we don't have right now. > >Anybody willing to look into this, and get rid of that __devexit_p() >thing? > (thinking vaguely long-term) I wonder if mochel already code for this, or has thought about this... Just like suspend, IMO we ideally should use the device tree to shutdown the system, agreed? Further, I wonder if the reboot/shutdown notifiers can be replaced with device tree control over those events... Jeff - 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/