All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Dave Jones <davej@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: __init dependencies (was: Re: [PATCH] find_isa_irq_pin can't be )__init
Date: Mon, 11 Oct 2004 13:33:58 +0200 (MEST)	[thread overview]
Message-ID: <Pine.GSO.4.61.0410111333260.19312@waterleaf.sonytel.be> (raw)
In-Reply-To: <20041010225717.GA27705@redhat.com>

On Sun, 10 Oct 2004, Dave Jones wrote:
> As spotted by one of our Fedora users, we sometimes
> oops during shutdown (http://www.roberthancock.com/kerneloops.png)
> because disable_IO_APIC() wants to call find_isa_irq_pin(),
> which we threw away during init.

I guess it's about time for a tool to autodetect __init dependencies?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2004-10-11 11:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 22:57 [PATCH] find_isa_irq_pin can't be __init Dave Jones
2004-10-11 11:33 ` Geert Uytterhoeven [this message]
2004-10-11 19:12   ` __init dependencies (was: Re: [PATCH] find_isa_irq_pin can't be )__init Andrew Morton
2004-10-11 19:16     ` Dave Jones
2004-10-11 19:17     ` __init dependencies Randy.Dunlap
2004-10-12  4:04       ` Randy.Dunlap
2004-10-12  4:19         ` Andrew Morton
2004-10-12  6:06         ` Keith Owens
2004-10-20 16:08           ` [PATCH] __init dependencies: ignore __param Randy.Dunlap

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=Pine.GSO.4.61.0410111333260.19312@waterleaf.sonytel.be \
    --to=geert@linux-m68k.org \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.