public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Matthew Garrett <mjg@redhat.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
	linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 1/2] suspend: Move NVS save/restore code to generic suspend functionality
Date: Sun, 30 May 2010 17:37:18 +0300	[thread overview]
Message-ID: <1275230238.14907.8.camel@maxim-laptop> (raw)
In-Reply-To: <1275078735-1866-1-git-send-email-mjg@redhat.com>

On Fri, 2010-05-28 at 16:32 -0400, Matthew Garrett wrote: 
> Saving platform non-volatile state may be required for suspend to RAM as
> well as hibernation. Move it to more generic code.


Since the other patch 'ACPI / EC / PM: Fix race between EC transactions
and system suspend' is now merged, this should be rebased on top of it
(I did the opposite....)

.... 
> diff --git a/kernel/power/nvs.c b/kernel/power/nvs.c
> new file mode 100644
> index 0000000..1836db6
> --- /dev/null
> +++ b/kernel/power/nvs.c
> @@ -0,0 +1,136 @@
> +/*
> + * linux/kernel/power/hibernate_nvs.c - Routines for handling NVS memory
This should be updated (I did in the version I posted) 
> + *
> + * Copyright (C) 2008,2009 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
> + *
> + * This file is released under the GPLv2.
> + */
> +
> +#include <linux/io.h>
> +#include <linux/kernel.h>
> +#include <linux/list.h>
> +#include <linux/mm.h>
> +#include <linux/slab.h>
> +#include <linux/suspend.h>
> +
............


Best regards,
Maxim Levitsky


  parent reply	other threads:[~2010-05-30 14:37 UTC|newest]

Thread overview: 25+ 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
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 ` Maxim Levitsky [this message]
2010-06-04 19:11   ` [PATCH 1/2] suspend: Move NVS save/restore code to generic suspend functionality 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 1/2] suspend: Move NVS save/restore code to generic suspend functionality Maxim Levitsky
2010-06-01 21:31   ` Rafael J. Wysocki
2010-06-01 21:52     ` Maxim Levitsky
2010-06-01 22:40       ` Rafael J. Wysocki
2010-06-01 22:46         ` Maxim Levitsky
2010-06-01 23:34           ` Rafael J. Wysocki

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=1275230238.14907.8.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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