public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trivial, update the comment in kthread_stop()
Date: Tue, 23 Jun 2009 13:21:10 +0930	[thread overview]
Message-ID: <200906231321.11313.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090619005113.GA12208@redhat.com>

On Fri, 19 Jun 2009 10:21:13 am Oleg Nesterov wrote:
> "kthreads: rework kthread_stop()"
> commit 63706172f332fd3f6e7458ebfb35fa6de9c21dc5 removed the limitation,
> but forgot to update the comment.
>
> Since that commit it is OK to use kthread_stop() even if kthread can exit
> itself.
>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>

Thanks, I've dropped this in my queue with other misc bits, but I really 
consider you to own kthread these days.

Thanks!
Rusty.

      reply	other threads:[~2009-06-23  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  0:51 [PATCH] trivial, update the comment in kthread_stop() Oleg Nesterov
2009-06-23  3:51 ` Rusty Russell [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=200906231321.11313.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.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