public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Anders Gustafsson <andersg@0x63.nu>,
	arjanv@redhat.com, linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: [PATCH] devexit fixes in i82092.c
Date: Fri, 15 Mar 2002 21:25:35 -0500	[thread overview]
Message-ID: <3C92AD1F.30909@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203151659060.1379-100000@home.transmeta.com>

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







  reply	other threads:[~2002-03-16  2:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16  0:57 [PATCH] devexit fixes in i82092.c Anders Gustafsson
2002-03-16  1:00 ` Linus Torvalds
2002-03-16  2:25   ` Jeff Garzik [this message]
2002-03-16  7:40     ` Linus Torvalds
2002-03-16  7:51       ` Keith Owens
2002-03-16  8:13         ` Linus Torvalds
2002-03-16  9:00           ` Jeff Garzik
2002-03-16  9:50           ` Keith Owens
2002-03-25 19:15           ` Patrick Mochel
2002-03-16  8:51       ` Jeff Garzik
2002-03-16 17:35         ` Alan Cox
2002-03-16 17:31           ` Jeff Garzik
2002-03-25 19:19           ` Patrick Mochel
2002-03-16  9:40       ` Arjan van de Ven
2002-03-22 15:47         ` Pavel Machek
2002-03-16 10:32       ` David Woodhouse
2002-03-16 19:27     ` Eric W. Biederman
2002-03-16 21:00       ` Alan Cox
2002-03-16 22:03         ` Eric W. Biederman
2002-03-16 22:28           ` Alan Cox
2002-03-16 22:16             ` Eric W. Biederman
2002-03-16 22:26             ` Linus Torvalds
2002-03-16 23:00               ` Eric W. Biederman
2002-03-16 23:15               ` Dave Jones
2002-03-21 15:12                 ` Pavel Machek
2002-03-25 19:02     ` Patrick Mochel
  -- strict thread matches above, loose matches on Subject: below --
2002-03-24 23:36 Alexander Stohr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C92AD1F.30909@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=andersg@0x63.nu \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=torvalds@transmeta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox