From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
pm list <linux-pm@lists.linux-foundation.org>,
Nigel Cunningham <nigel@nigel.suspend2.net>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: Hibernation and suspend patchset
Date: Thu, 03 May 2007 21:08:55 +0200 [thread overview]
Message-ID: <1178219335.4575.4.camel@johannes.berg> (raw)
In-Reply-To: <200705011558.11170.rjw@sisk.pl>
Hi Rafael,
Some bugs with freezer_exempt:
kernel/softirq.c: In function ‘ksoftirqd’:
kernel/softirq.c:515: warning: implicit declaration of function ‘freezer_exempt’
[...]
Maybe some header file they all use pulls in freezer.h on x86 but not on
powerpc? This fixes it.
--- linux-2.6-git.orig/drivers/block/loop.c 2007-05-03 15:30:23.274123904 +0200
+++ linux-2.6-git/drivers/block/loop.c 2007-05-03 15:30:43.015123904 +0200
@@ -74,6 +74,7 @@
#include <linux/highmem.h>
#include <linux/gfp.h>
#include <linux/kthread.h>
+#include <linux/freezer.h>
#include <asm/uaccess.h>
--- linux-2.6-git.orig/drivers/ieee1394/ieee1394_core.c 2007-05-03 15:30:23.423123904 +0200
+++ linux-2.6-git/drivers/ieee1394/ieee1394_core.c 2007-05-03 15:30:50.023123904 +0200
@@ -34,6 +34,7 @@
#include <linux/kthread.h>
#include <linux/preempt.h>
#include <linux/time.h>
+#include <linux/freezer.h>
#include <asm/system.h>
#include <asm/byteorder.h>
--- linux-2.6-git.orig/drivers/scsi/scsi_error.c 2007-05-03 15:30:23.498123904 +0200
+++ linux-2.6-git/drivers/scsi/scsi_error.c 2007-05-03 15:30:54.423123904 +0200
@@ -24,6 +24,7 @@
#include <linux/interrupt.h>
#include <linux/blkdev.h>
#include <linux/delay.h>
+#include <linux/freezer.h>
#include <scsi/scsi.h>
#include <scsi/scsi_cmnd.h>
--- linux-2.6-git.orig/kernel/softirq.c 2007-05-03 15:30:23.187123904 +0200
+++ linux-2.6-git/kernel/softirq.c 2007-05-03 15:30:37.470123904 +0200
@@ -18,6 +18,7 @@
#include <linux/rcupdate.h>
#include <linux/smp.h>
#include <linux/tick.h>
+#include <linux/freezer.h>
#include <asm/irq.h>
/*
--- linux-2.6-git.orig/kernel/softlockup.c 2007-05-03 15:30:23.348123904 +0200
+++ linux-2.6-git/kernel/softlockup.c 2007-05-03 15:30:46.214123904 +0200
@@ -13,6 +13,7 @@
#include <linux/kthread.h>
#include <linux/notifier.h>
#include <linux/module.h>
+#include <linux/freezer.h>
static DEFINE_SPINLOCK(print_lock);
--- wireless-dev.orig/drivers/char/apm-emulation.c 2007-05-03 20:01:08.309154963 +0200
+++ wireless-dev/drivers/char/apm-emulation.c 2007-05-03 20:01:14.119154963 +0200
@@ -27,6 +27,7 @@
#include <linux/completion.h>
#include <linux/kthread.h>
#include <linux/delay.h>
+#include <linux/freezer.h>
#include <asm/system.h>
next prev parent reply other threads:[~2007-05-03 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 13:58 Hibernation and suspend patchset Rafael J. Wysocki
2007-05-01 14:04 ` Alan Stern
2007-05-01 14:11 ` Rafael J. Wysocki
2007-05-03 13:38 ` Johannes Berg
2007-05-04 11:36 ` Rafael J. Wysocki
2007-05-04 11:43 ` Johannes Berg
2007-05-03 19:08 ` Johannes Berg [this message]
2007-05-04 11:34 ` Rafael J. Wysocki
2007-05-04 12:02 ` Rafael J. Wysocki
2007-05-04 12:05 ` Johannes Berg
2007-05-04 12:15 ` Rafael J. Wysocki
2007-05-04 12:15 ` Johannes Berg
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=1178219335.4575.4.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=penberg@cs.helsinki.fi \
--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