From: ebiederm@xmission.com (Eric W. Biederman)
To: Jes Sorensen <jes@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"<Andrew Morton" <akpm@osdl.org>,
containers@lists.osdl.org, Oleg Nesterov <oleg@tv-sign.ru>,
linux-kernel@vger.kernel.org, Tony Luck <tony.luck@intel.com>,
rja@sgi.com, holt@sgi.com, dcn@sgi.com,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64 sn xpc: Convert to use kthread API.
Date: Mon, 23 Apr 2007 17:36:00 +0000 [thread overview]
Message-ID: <m1r6qbvvr3.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <462CE8D5.8040300@sgi.com> (Jes Sorensen's message of "Mon, 23 Apr 2007 19:11:49 +0200")
Jes Sorensen <jes@sgi.com> writes:
>
> Like with the previous patch from Eric, I'm CC'ing the correct people
> for this patch (forwarded it in a seperate email). CC'ing irrelevant
> lists such as containers@ and not linux-ia64@ makes it somewhat
> difficult to get proper reviews of these things.
containers is actually relevant because everything not being converted
to a kthread API is actually show stopper issue for the development of
the pid namespace because of the usage of pids by kernel_thread, and
the apparent impossibility to fix daemonize to sort this out.
Now I do agree linux-ia64 is also relevant.
> Russ/Dean/Robin - could one of you provide some feedback to this one
> please.
Eric
next prev parent reply other threads:[~2007-04-23 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1slawn9eb.fsf@ebiederm.dsl.xmission.com>
[not found] ` <1176969574439-git-send-email-ebiederm@xmission.com>
[not found] ` <20070422203647.GC23015@infradead.org>
2007-04-23 17:11 ` [PATCH] ia64 sn xpc: Convert to use kthread API Jes Sorensen
2007-04-23 17:36 ` Eric W. Biederman [this message]
2007-04-23 19:03 ` Russ Anderson
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=m1r6qbvvr3.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=containers@lists.osdl.org \
--cc=dcn@sgi.com \
--cc=hch@infradead.org \
--cc=holt@sgi.com \
--cc=jes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=rja@sgi.com \
--cc=tony.luck@intel.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