Linux ACPI
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Matthew Garrett <mjg@redhat.com>,
	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: Thu, 10 Jun 2010 11:11:59 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1006101110190.4129@localhost.localdomain> (raw)
In-Reply-To: <1275751718.10792.0.camel@maxim-laptop>

On Sat, 5 Jun 2010, Maxim Levitsky wrote:

> On Fri, 2010-06-04 at 15:11 -0400, Len Brown wrote: 
> > > 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....)
> > 
> > Maxim,
> > Since your system needs both these fixes, and they are merged together
> > in the acpi git tree, it would be great if you could test that tree
> > and let me know if we got it right.
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git test


> Which kernel do you expect these patches to land on?

the test tree above is in linux-next now.
there are some patches that will be 2.6.36 in there,
but I was considereing this one for 2.6.35-rc3 --
though your e-mail with a stack trace has caused me to pause --
did I mis-merge it?

thanks,
-Len Brown, Intel Open Source Technology Center

  reply	other threads:[~2010-06-10 15:12 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 ` [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 [this message]
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=alpine.LFD.2.00.1006101110190.4129@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --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