From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI: Store NVS state even when entering suspend to RAM
Date: Sun, 30 May 2010 15:51:43 +0100 [thread overview]
Message-ID: <20100530145142.GA32078@srcf.ucam.org> (raw)
In-Reply-To: <1275230404.14907.11.camel@maxim-laptop>
On Sun, May 30, 2010 at 05:40:04PM +0300, Maxim Levitsky wrote:
> Just one note, I am sure somebody will ask for s3_no_nvs option, just
> like s4_no_nvs.
I'd be surprised. Better to add the option when we think it's needed.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-05-30 14:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 20:32 [PATCH 1/2] suspend: Move NVS save/restore code to generic suspend functionality Matthew Garrett
2010-05-28 20:32 ` [PATCH 2/2] ACPI: Store NVS state even when entering suspend to RAM Matthew Garrett
2010-05-30 14:40 ` Maxim Levitsky
2010-05-30 14:51 ` Matthew Garrett [this message]
2010-06-02 3:32 ` Henrique de Moraes Holschuh
2010-06-02 10:15 ` Maxim Levitsky
2010-06-02 11:47 ` Matthew Garrett
2010-06-02 13:06 ` Maxim Levitsky
2010-06-04 18:23 ` Len Brown
2010-06-10 9:41 ` Maxim Levitsky
2010-05-30 14:37 ` [PATCH 1/2] suspend: Move NVS save/restore code to generic suspend functionality Maxim Levitsky
2010-06-04 19:11 ` Len Brown
2010-06-04 21:27 ` Maxim Levitsky
2010-06-04 21:30 ` Maxim Levitsky
2010-06-05 15:28 ` Maxim Levitsky
2010-06-10 15:11 ` Len Brown
2010-06-10 15:21 ` Maxim Levitsky
2010-06-04 18:22 ` Len Brown
2010-06-04 21:48 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2010-06-01 18:19 [PATCH] Store BIOS NVS area over s2ram [V2] Maxim Levitsky
2010-06-01 18:22 ` [PATCH 2/2] ACPI: Store NVS state even when entering suspend to RAM Maxim Levitsky
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=20100530145142.GA32078@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maximlevitsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).