mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
	Paul Mackerras <paulus@samba.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kthread: convert stop_machine into a kthread
Date: Fri, 16 Jun 2006 07:54:03 -0500	[thread overview]
Message-ID: <20060616125403.GA16194@sergelap.austin.ibm.com> (raw)
In-Reply-To: <1150430429.10290.23.camel@localhost.localdomain>

Quoting Rusty Russell (rusty@rustcorp.com.au):
> On Thu, 2006-06-15 at 22:04 -0500, Serge E. Hallyn wrote:
> > Quoting Rusty Russell (rusty@rustcorp.com.au):
> > > Seems like change for change's sake, to me, *and* it added more code
> > > than it removed.
> > 
> > So if kernel_thread is really going to be removed, how else should this
> > be done?  Just clone?
> 
> Sorry, is kernel_thread going to be removed, or just not exported to
> modules?  What's kthread going to use?
> 
> Confused,
> Rusty.

Hah.

Yes, I see.  I misread.  So I should be focusing on modules  :)

Really, all *I* care about is cases where the resulting pid is cached
as a pointer to the thread, which it wasn't here anyway.  

thanks, sorry for the noise.

-serge

  reply	other threads:[~2006-06-16 12:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17553.56625.612931.136018@cargo.ozlabs.ibm.com>
2006-06-16  1:04 ` Rusty Russell
2006-06-16  3:04   ` Serge E. Hallyn
2006-06-16  3:54     ` Paul Mackerras
2006-06-16  4:00     ` Rusty Russell
2006-06-16 12:54       ` Serge E. Hallyn [this message]
2006-06-18 12:12         ` Eric W. Biederman
2006-06-15 14:43 Serge E. Hallyn
2006-06-20  3:14 ` Andrew Morton
2006-06-20  3:20   ` Erik Ohrnberger
2006-06-20  8:27   ` Serge E. Hallyn
2006-06-20  8:40     ` Andrew Morton
2006-06-20 16:27       ` Serge E. Hallyn
2006-06-20 22:42         ` Andrew Morton
2006-06-21  0:52           ` Serge E. Hallyn
2006-06-21  1:18             ` Andrew Morton
2006-06-21  1:44               ` Serge E. Hallyn

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=20060616125403.GA16194@sergelap.austin.ibm.com \
    --to=serue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=rusty@rustcorp.com.au \
    /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®