[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <542D1EC4.10100@citrix.com>
Date: Thu, 2 Oct 2014 10:45:40 +0100
From: David Vrabel <david.vrabel@...rix.com>
To: Guenter Roeck <linux@...ck-us.net>, <linux-kernel@...r.kernel.org>
CC: <linux-mips@...ux-mips.org>, <linux-ia64@...r.kernel.org>,
<linux-c6x-dev@...ux-c6x.org>, <linux-parisc@...r.kernel.org>,
<linux-pm@...r.kernel.org>, <linux-sh@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, <xen-devel@...ts.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
<linux-metag@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [Xen-devel] [RFC PATCH 14/16] x86/xen: support poweroff through
poweroff handler call chain
On 30/09/14 19:00, Guenter Roeck wrote:
> The kernel core now supports a poweroff handler call chain
> to remove power from the system. Call it if pm_power_off
> is set to NULL.
>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
> Cc: Boris Ostrovsky <boris.ostrovsky@...cle.com>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Ingo Molnar <mingo@...hat.com>
> Cc: H. Peter Anvin <hpa@...or.com>
> Signed-off-by: Guenter Roeck <linux@...ck-us.net>
> ---
> arch/x86/xen/enlighten.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> index c0cb11f..645d00f 100644
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -1322,6 +1322,8 @@ static void xen_machine_power_off(void)
> {
> if (pm_power_off)
> pm_power_off();
> + else
> + do_kernel_poweroff();
Why isn't this if (pm_power_off) check in do_kernel_poweroff()?
That way when you finally remove pm_power_off you need only update one
place. A quick skim of the other archs suggest this would work for them
too.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists