mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>
Cc: Andrew Morton <akpm@digeo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Rename PF_IOTHREAD.
Date: Mon, 19 Apr 2004 11:09:34 +0200	[thread overview]
Message-ID: <20040419090933.GA18158@elf.ucw.cz> (raw)
In-Reply-To: <1082357671.2620.10.camel@laptop-linux.wpcb.org.au>

Hi!

> A few weeks ago, Pavel and I agreed that PF_IOTHREAD should be renamed
> to PF_NOFREEZE. This reflects the fact that some threads so marked
> aren't actually used for IO while suspending, but simply shouldn't be
> frozen. This patch, against 2.6.5 vanilla, applies that change. In the
> refrigerator calls, the actual value doesn't matter (so long as it's
> non-zero) and it makes more sense to use PF_FREEZE so I've used that.
> 
> Please apply.

Patch looks good. [Except that I'm not sure if this hunk will apply;
there were changes for ^Z in this area].
								Pavel


> diff -ruN linux-2.6.5/kernel/power/process.c linux-2.6.5-NoFreeze/kernel/power/process.c
> --- linux-2.6.5/kernel/power/process.c	2004-01-13 14:16:35.000000000 +1100
> +++ linux-2.6.5-NoFreeze/kernel/power/process.c	2004-04-19 16:47:24.000000000 +1000
> @@ -28,7 +28,7 @@
>  static inline int freezeable(struct task_struct * p)
>  {
>  	if ((p == current) || 
> -	    (p->flags & PF_IOTHREAD) || 
> +	    (p->flags & PF_NOFREEZE) || 
>  	    (p->state == TASK_ZOMBIE) ||
>  	    (p->state == TASK_DEAD))
>  		return 0;

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

      reply	other threads:[~2004-04-19  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19  6:54 Nigel Cunningham
2004-04-19  9:09 ` Pavel Machek [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=20040419090933.GA18158@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@users.sourceforge.net \
    /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®