mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <christoph@lameter.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 2/4] Task notifier against mm: Implement todo list in task_struct
Date: Sat, 30 Jul 2005 08:43:37 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0507300843100.24809@graphe.net> (raw)
In-Reply-To: <20050730112241.GA1830@elf.ucw.cz>

On Sat, 30 Jul 2005, Pavel Machek wrote:

> No wonder when -mm already contains:
> 
> /*
>  * Check if there is a request to freeze a process
>  */
> static inline int freezing(struct task_struct *p)
> {
>         return test_ti_thread_flag(p->thread_info, TIF_FREEZE);
> }

Yes I told you to remove the TIF_FREEZE patch.


  parent reply	other threads:[~2005-07-30 15:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 20:32 [PATCH 1/4] Task notifier against mm: Allow notifier to remove itself Christoph Lameter
2005-07-29 20:33 ` [PATCH 2/4] Task notifier against mm: Implement todo list in task_struct Christoph Lameter
2005-07-29 20:34   ` [PATCH 3/4] Task notifier against mm: Make suspend code SMP safe using todo list Christoph Lameter
2005-07-29 20:35     ` [PATCH 4/4] Task notifier against mm: s/try_to_freeze/try_todo_list in some driver Christoph Lameter
2005-07-30 11:22   ` [PATCH 2/4] Task notifier against mm: Implement todo list in task_struct Pavel Machek
2005-07-30 11:26     ` Pavel Machek
2005-07-30 15:43     ` Christoph Lameter [this message]
2005-07-30 16:10       ` Pavel Machek
2005-07-30 16:18         ` Christoph Lameter
2005-07-30 16:22           ` Pavel Machek
2005-08-01 18:43             ` Christoph Lameter
2005-08-08  9:43               ` Pavel Machek
2005-08-08 15:49                 ` Christoph Lameter
2005-08-08 22:09                   ` Pavel Machek

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=Pine.LNX.4.62.0507300843100.24809@graphe.net \
    --to=christoph@lameter.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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®