mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: pm list <linux-pm@lists.linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: [PATCH 0/5] Async suspend/resume tree
Date: Sun, 13 Dec 2009 23:38:30 +0100	[thread overview]
Message-ID: <200912132338.30921.rjw@sisk.pl> (raw)

Hi,

After the async suspend/resume patches in my original pull request had been
rejected, I created an async suspend tree to save store some async-related
patches in there so that they don't get lost.  Today I rebased it on top of the
latest async suspend/resume patch posted here:
http://lkml.org/lkml/2009/12/12/124

It is on top of my linux-next tree containing the patches that I'm planning to
include in the next pull request.

At the moment, the following patches are in the async tree at:
http://git.kernel.org/?p=linux/kernel/git/rafael/suspend-2.6.git;a=shortlog;h=refs/heads/async

Please let me know if there are objections to any of them.

Thanks,
Rafael


             reply	other threads:[~2009-12-13 22:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13 22:38 Rafael J. Wysocki [this message]
2009-12-13 22:39 ` [PATCH 1/5] PM: Asynchronous suspend and resume of devices Rafael J. Wysocki
2009-12-13 22:40 ` [PATCH 2/5] PM: Measure device suspend and resume times Rafael J. Wysocki
2009-12-13 22:40 ` [PATCH 3/5] PM: Add debug printouts to async suspend and resume code paths Rafael J. Wysocki
2009-12-13 22:41 ` [PATCH 4/5] PM: Add a switch for disabling/enabling asynchronous suspend/resume Rafael J. Wysocki
2009-12-13 22:42 ` [PATCH 5/5] PM: Add facility for advanced testing of async suspend/resume Rafael J. Wysocki
2009-12-15 21:56 ` [PATCH] PM: Allow serio input devices to suspend/resume asynchronously (was: Re: [PATCH 0/5] Async suspend/resume tree) 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=200912132338.30921.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.org \
    /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
all inboxes | Powered by JetHome®