public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [Announce]: Software Suspend 2.1-rc1 for 2.6.8.1 and 2.6.9-rc3.
Date: Sun, 03 Oct 2004 09:45:17 +1000	[thread overview]
Message-ID: <1096760717.8556.9.camel@desktop.cunninghams> (raw)

[-- Attachment #1: Type: text/plain, Size: 587 bytes --]

Hi all.

Software suspend 2.1-rc1 for the above kernels has been uploaded to
http://softwaresuspend.berlios.de.

Changes since 2.0.0.109 are pretty minimal, amounting almost exclusively
to compile fixes. There is no new functionality, but some refrigerator
calls have been fixed (hvc console and pdflush in particular).

Since the announcement on the suspend-devel list, one minor issue has
been found which applies to the 2.6.8.1 version only. And additional
patch (which can be applied after the others or popped into the patch
directory before applying) is attached.

Regards,

Nigel

[-- Attachment #2: 999 --]
[-- Type: text/x-patch, Size: 575 bytes --]

diff -ruN 999-old/kernel/power/suspend.c 999-new/kernel/power/suspend.c
--- 999-old/kernel/power/suspend.c	2004-09-28 08:21:43.000000000 +1000
+++ 999-new/kernel/power/suspend.c	2004-09-28 08:21:33.000000000 +1000
@@ -325,10 +325,11 @@
 
 	/* Now check for graphics class devices, so we can keep the display on while suspending */
 	class = class_find("graphics");
-	if (class)
+	if (class) {
 		list_for_each_entry(class_dev, &class->children, node)
 			device_switch_trees(class_dev->dev, suspend_device_tree);
-	class_put(class);
+		class_put(class);
+	}
 	return 0;
 }
 

                 reply	other threads:[~2004-10-02 23:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1096760717.8556.9.camel@desktop.cunninghams \
    --to=ncunningham@linuxmail.org \
    --cc=linux-kernel@vger.kernel.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