From: Matt Fleming <matt@codeblueprint.co.uk>
To: "Chen, Yu C" <yu.c.chen@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"Zhang, Rui" <rui.zhang@intel.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mark Salter <msalter@redhat.com>
Subject: Re: [PATCH][RFC,v4] ACPI / PM: Introduce efi poweroff for HW-full platforms without _S5
Date: Mon, 14 Mar 2016 20:00:33 +0000 [thread overview]
Message-ID: <20160314200033.GG2619@codeblueprint.co.uk> (raw)
In-Reply-To: <36DF59CE26D8EE47B0655C516E9CE640286D442A@shsmsx102.ccr.corp.intel.com>
On Fri, 11 Mar, at 04:33:46PM, Chen, Yu C wrote:
>
> There is a future Base-IA platform, we are planning to skip
> implementing the SLP_TYP register and the S5 object. (already there
> will be no S3 and no S4)
Cool. This is really valuable information that should go into the
commit message.
Because if this is the rationale for the change, I don't see why we'd
need to provide the default stuff. Instead we should just enforce EFI
reboot, and only add the pm_poweroff_default hook if there is an
explicit user in the future, IMO.
next prev parent reply other threads:[~2016-03-14 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 9:05 [PATCH][RFC,v4] ACPI / PM: Introduce efi poweroff for HW-full platforms without _S5 Chen Yu
2016-03-11 9:05 ` Chen Yu
2016-03-11 15:55 ` Matt Fleming
2016-03-11 16:33 ` Chen, Yu C
2016-03-14 20:00 ` Matt Fleming [this message]
2016-03-16 5:59 ` Chen, Yu C
2016-03-17 14:39 ` Matt Fleming
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=20160314200033.GG2619@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=msalter@redhat.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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 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.