From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Peter Osterlund <petero2@telia.com>
Cc: Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Per kthread freezer flags
Date: Sat, 31 Jul 2004 08:15:41 +1000 [thread overview]
Message-ID: <1091225740.11580.0.camel@laptop.cunninghams> (raw)
In-Reply-To: <m3llh1k845.fsf@telia.com>
Hi.
On Fri, 2004-07-30 at 22:11, Peter Osterlund wrote:
> Yes. What about this code in the main loop in kcdrwd?
>
> /* make swsusp happy with our thread */
> if (current->flags & PF_FREEZE)
> refrigerator(PF_FREEZE);
>
> Should it still be there when the task is marked as PF_NOFREEZE?
No, it's not needed if the thread is NOFREEZE.
Regards,
Nigel
prev parent reply other threads:[~2004-07-30 22:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 7:22 [Patch] Per kthread freezer flags Nigel Cunningham
2004-07-28 21:20 ` Andrew Morton
2004-07-28 22:25 ` Nigel Cunningham
2004-07-28 22:30 ` Felipe Alfaro Solana
2004-07-28 22:27 ` Nigel Cunningham
2004-07-28 22:36 ` Nigel Cunningham
2004-07-28 23:21 ` Felipe Alfaro Solana
2004-07-29 0:46 ` Nigel Cunningham
2004-07-29 10:02 ` Felipe Alfaro Solana
2004-07-29 12:11 ` Nigel Cunningham
2004-07-29 16:10 ` Felipe Alfaro Solana
2004-07-29 22:39 ` Nigel Cunningham
2004-07-30 8:12 ` Felipe Alfaro Solana
2004-07-29 22:57 ` Felipe Alfaro Solana
2004-07-29 23:01 ` Nigel Cunningham
2004-07-29 19:04 ` Pavel Machek
2004-07-29 22:24 ` Nigel Cunningham
2004-07-29 22:44 ` Pavel Machek
2004-07-29 22:46 ` Nigel Cunningham
2004-07-29 23:25 ` [Patch] Per kthread freezer flags (Version 2) Nigel Cunningham
2004-07-30 9:18 ` Pavel Machek
2004-07-31 16:53 ` Felipe Alfaro Solana
2004-07-30 12:11 ` [Patch] Per kthread freezer flags Peter Osterlund
2004-07-30 22:15 ` Nigel Cunningham [this message]
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=1091225740.11580.0.camel@laptop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=petero2@telia.com \
/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