From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Jones <davej@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: suspicious behaviour in pcwd driver.
Date: Tue, 23 Aug 2005 09:26:22 +1000 [thread overview]
Message-ID: <1124753182.5189.63.camel@gaston> (raw)
In-Reply-To: <20050822183006.GB27344@redhat.com>
> Export machine_power_off() on ppc64, as the pcwd watchdog driver needs it.
>
> Signed-off-by: Dave Jones <davej@redhat.com>
>
> --- linux-2.6.12/arch/ppc64/kernel/setup.c~ 2005-08-09 17:37:36.000000000 -0400
> +++ linux-2.6.12/arch/ppc64/kernel/setup.c 2005-08-09 17:37:53.000000000 -0400
> @@ -706,6 +706,7 @@ void machine_power_off(void)
> local_irq_disable();
> while (1) ;
> }
> +EXPORT_SYMBOL(machine_power_off);
>
> void machine_halt(void)
> {
>
In fact, we need that for the G5 thermal driver too. I wonder why/how
this export got removed ... Some over-zealous janitors ?
Hrm... /me plays with gitk
Ahhh, ok, so that is this patch:
<<
machine_restart, machine_halt and machine_power_off are machine
specific hooks deep into the reboot logic, that modules
have no business messing with. Usually code should be calling
kernel_restart, kernel_halt, kernel_power_off, or
emergency_restart. So don't export machine_restart,
machine_halt, and machine_power_off so we can catch buggy users.
>>
Well, I think for now, it's safe for therm_pm72 to call
machine_power_off() in case of critical overtemp. I'll have a look at
kernel_* equivalents later.
Can you still slip that patch into 2.6.13 ?
Ben.
prev parent reply other threads:[~2005-08-22 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 18:30 suspicious behaviour in pcwd driver Dave Jones
2005-08-22 20:01 ` Dave Jones
2005-08-25 12:00 ` Pavel Machek
2005-08-22 23:26 ` Benjamin Herrenschmidt [this message]
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=1124753182.5189.63.camel@gaston \
--to=benh@kernel.crashing.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.