From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>,
Matthew Garrett <mjg59-kernel@srcf.ucam.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Preserve ACPI NVS region over S3
Date: Fri, 28 May 2010 21:25:08 +0100 [thread overview]
Message-ID: <20100528202508.GA3025@srcf.ucam.org> (raw)
In-Reply-To: <1275077971.20606.20.camel@maxim-laptop>
Excellent. I'll send those patches.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2010-05-28 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 20:19 Preserve ACPI NVS region over S3 Maxim Levitsky
2010-05-28 20:22 ` [PATCH 1/2] ACPI: Save/Restore NVS area on suspend/resume too Maxim Levitsky
2010-06-21 15:53 ` [linux-pm] " Pavel Machek
2010-06-22 12:06 ` Matthew Garrett
2010-06-22 15:19 ` Maxim Levitsky
2010-05-28 20:22 ` [PATCH 2/2] ACPI / EC / PM: Fix race between EC transactions and system suspend Maxim Levitsky
2010-05-28 20:25 ` Matthew Garrett [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=20100528202508.GA3025@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=maximlevitsky@gmail.com \
--cc=mjg59-kernel@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).