From: Pavel Machek <pavel@ucw.cz>
To: Adrian Bunk <bunk@kernel.org>
Cc: rjw@sisk.pl, linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] make kernel_shutdown_prepare() static
Date: Wed, 24 Oct 2007 20:22:26 +0200 [thread overview]
Message-ID: <20071024182226.GC5093@elf.ucw.cz> (raw)
In-Reply-To: <20071024162345.GV30533@stusta.de>
On Wed 2007-10-24 18:23:45, Adrian Bunk wrote:
> kernel_shutdown_prepare() can now become static.
>
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
ACK.
> diff --git a/include/linux/reboot.h b/include/linux/reboot.h
> index 85ea63f..b93b541 100644
> --- a/include/linux/reboot.h
> +++ b/include/linux/reboot.h
> @@ -59,8 +59,6 @@ extern void machine_crash_shutdown(struct pt_regs *);
> * Architecture independent implemenations of sys_reboot commands.
> */
>
> -extern void kernel_shutdown_prepare(enum system_states state);
> -
> extern void kernel_restart(char *cmd);
> extern void kernel_halt(void);
> extern void kernel_power_off(void);
> diff --git a/kernel/sys.c b/kernel/sys.c
> index 304b541..4c77ed2 100644
> --- a/kernel/sys.c
> +++ b/kernel/sys.c
> @@ -315,7 +315,7 @@ static void kernel_kexec(void)
> #endif
> }
>
> -void kernel_shutdown_prepare(enum system_states state)
> +static void kernel_shutdown_prepare(enum system_states state)
> {
> blocking_notifier_call_chain(&reboot_notifier_list,
> (state == SYSTEM_HALT)?SYS_HALT:SYS_POWER_OFF, NULL);
>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-10-24 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:23 [2.6 patch] make kernel_shutdown_prepare() static Adrian Bunk
2007-10-24 18:22 ` Pavel Machek [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=20071024182226.GC5093@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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